2011/12/19 Martin Cooper <mart...@apache.org>: > Actually, no, not quite. > > A really, really long time ago, with early Struts 1 releases, we used > to designate quality with the initial build. We got out of that bad > habit quite a few years ago. The process I was referring to, which was > used for later Struts 1 and earlier Struts 2 builds, was: > > - RM: Perform the (Maven) release process using next build number. > - RM: Announce a new Test Build. > - RM: Wait for about a week to give everyone a chance to download and test it. > - All: Download, test, and provide feedback if appropriate. > - RM: If no show-stoppers reported, start a vote thread for build > quality designation. > - All: Vote on quality - GA, Beta, Alpha, or just stay at test build. > - RM: If the vote result is for an ASF release (i.e. not test build), > update site, announce > - RM: If the vote result is for GA, push to central
Thanks Martin, I added your points to the guideline [1] [1] https://cwiki.apache.org/confluence/display/WW/Building+Struts+2+-+Normal+release#BuildingStruts2-Normalrelease-Announceavailability Kind regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org