Hi,
Release process A:
- the project is in 1.0-SNAPSHOT version
- near the end of the iteration, we start an "acceptance review" (a
long phase of testing). if it is ok a maven release is done, if not
corrections are made on the snapshot.
That release process is not good because the deploy team is not very
happy happy to "lose" the version they test and use a fresh new release.
I know that it's only a re-packaging with new versions names but they do
not like it.
In fact, what they need is to do all their tests with one version and
use that version at the end.
So we change our release process to send maven release "1.0-RC1",
"1-0-RC2".. to the deploy team. So when everything is ok they have a
real released maven version.
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.
Well may be I can release "1.0" version all the time and use the svn
revision as a buildnumber I display somewhere in the app, but it sound
not very maven way to release "1.0" over and over. I know that archiva
allow that, but I think that the .m2 repository won't be updated.
Do you facing the same kind of problems?
--
Julien Graglia
NetCeler
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
