2009/9/15 Julien Graglia <[email protected]>: > This is release process B : > - the project is in 1.0-SNAPSHOT version > - before the end of the iteration, we release a release candidate named > 1.0-RC1 and we start 1.0-RC2-SNAPSHOT > - the acceptance tests are done on the 1.0-RC1. if everything is ok, > the deploy team can use that release and the dev team can start > 1.1-SNAPSHOT. > - if the acceptance tests failed, corrections are made onto the > 1.0-RC2-SNAPSHOT, then the 1.0-RC2 is released ...etc.... > > That's simple and easy, but we still have some problems with that : the > name of the version : they don't like "1.0-RC6" or "1.0-RC2", they > prefer to deliver version "1.0" to the client.
You may think to separate the "quality" of the software you release from the "version number". For instance, at Tiles we use x.y.z version numbers when we do the release process. After the release, we decide what is the quality, and disclaim it in the website and in announcements. For instance: Tiles 2.0.0 was a test build (not released). Tiles 2.0.1 was a test build Tiles 2.0.2 was Alpha quality. Tiles 2.0.3 was Alpha quality. Tiles 2.0.4 was Beta quality Tiles 2.0.5 was GA quality HTH Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
