> ...that is we decide when a release is ready and > use the release plugin to do this. The CI is only producing > snapshots on a constant basis.
So your formal releases are produced by manually running the release plugin? And if it fails, you manually do a rollback, depending on the failure? Some of our teams wish to automate the creation of a release say every week and include all feature and bug fixes for that week in the release. The problem of course is that the release plugin commits changes to the trunk. If for whatever reason the formal build fails, and no person is there to immediately investigate and do a rollback, you could have your trunk in an bad state which is something we of course wish to avoid. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
