The Struts team has an interesting build policy. Instead of relase candidates they just do a minor build number. Then people vote on: alpha, beta or GA. So as you approach a release you have these minor "milestones" but they're not officially announced on the user lists, etc. We could update the website with a description of the alpha and beta releases and make them available in the nightly dir (like we did in the past for RC.) We wouldn't go to the trouble of mirroring or testing JSF 1.1 compatability until a positive GA vote.
There was a recent thread on roadmaps, etc. One thing that was mentioned on the struts-dev list that I agree with is that the person who designates a bug to be fixed in a particular version is taking responsibility for *actually* fixing that bug. This way your roadmap is based on firm committments of time instead of an idealistic wishlist that may take much much longer to accomplish. sean On 12/9/05, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]> wrote: > hmm... Milestone build ... I seem to connect that to a roadmap for a new > planned release. > > How about releasing "integration builds"? > > - nightly builds > somewhat "untested" (?) automatic builds > - integration builds > - some defined test havebeen successfully executed > - at least the sample-apps have been integrated with these builds > - milestone builds > - more extensive testing (including "end-users") > - issues fromthe roadmap can be ticked off > > just my 2cents > Alexander > > -----Original Message----- > From: Simon Kitching [mailto:[EMAIL PROTECTED] > Sent: Friday, December 09, 2005 5:07 AM > To: MyFaces Development > Subject: Milestone builds? > > Hi, > > What do people think about releasing a binary milestone build? > > Currently the SVN head is pretty stable. There are *many* great fixes > and enhancements since the 1.1.1 release, but people may be (rightly) > wary of trying to use SVN head as there's no guarantee it's workable at > any particular time. > > Releasing a "milestone" build every couple of months, where we run the > tests, the examples, wait a few days for any problem reports, then > publish it could be very useful without being a large burden to create. > > Opinions? > > Cheers, > > Simon >
