Lots of the "pain" when doing a release comes from the administrative side. Getting Jira issues in shape and tagged for the release, preparing release notes and docs export, fixing site texts, managing the vote process, doing announcements etc. In addition, there are some time consuming and maybe more automizable tasks such as signing assemblies, promoting files to the staging, mirroring and download areas along with subsequently fixing permissions and ownership. The actual technical deploy / assembly steps are not really complicated in the end (well, for 2.0.x they still sometimes are, 2.1.x does better here).
As I do from time to time some work an 2.0.x branch, which afaik is not covered any more by bamboo, I have set up my own little hudson CI for the 2.0.x branch, which works like a charm and delivers automated snapshots, and should theoretically be able to perform most of the "technical" release side. Still, the administrative side as described above remains very time consuming, and since we have clear rules on how to deal with releases, I see no way around investing this time. That said, I believe that doing automated snapshot / nightly builds (including assemblies) would help a lot on delivering a solution for early adopters, which in return would help to get very stable release candidates which are most likely to pass the GA votes - every release manager is IMO praying to have the release pass the vote, because preparing is hard and time consuming and he will have to do the whole cycle again if it does not pass. - Rene Am Mi, 22.10.2008, 04:58, schrieb Wendy Smoak: > On Tue, Oct 21, 2008 at 6:01 PM, Bob Tiernay <[EMAIL PROTECTED]> wrote: >> I get the sense that CI + Maven is a like wrestling with a slinky. Is >> this >> problem endemic to s2? What do other open source projects do to >> alleviate >> this? > > The release process here could be *much* simpler, but it's really hard > to change someone else's process. :) It's going to take someone to > volunteer to be release manager and refine the process and the build > once or twice. > > Compare to... http://cwiki.apache.org/ARCHIVA/archiva-release-process.html > > It really should be those two steps-- "mvn release:prepare" and "mvn > release:perform" > > The first thing I'd do is flip things around so that everything builds > by default, and use profiles to *exclude* things if necessary. But > since I'm pretty sure that would break Bamboo, I won't do it. I will > make time to help if someone wants to drive this. > > I think Maven and CI is pretty easy... Continuum or Hudson work fine, > and they both have integration with Maven release. But CI may be > problematic for releases here due to the PGP signing requirement-- you > wouldn't want to put your private signing key on a shared CI server. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)177-3194448 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
