Add automated tasks to release process to make sure we have the right set of dependencies:
- Test with both MRI and JRuby specs, since they use different dependency sets.
- For each dependency, verify that the Gem is available on the RubyForge server.
- That goes for platform variance, e.g. RJB has both ruby and win32 platform, both must be checked for existence.
- From dependency list determine the order in which dependencies will be loaded, and make sure the dependency list is in that order.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|112d 19h 19m||1||Assaf Arkin||26/Sep/08 21:18|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Assaf Arkin [ assafarkin ]|
|Field||Original Value||New Value|
|Fix Version/s||1.3.3 [ 12313289 ]|
|Fix Version/s||1.3.2 [ 12313159 ]|