commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Commons Wiki] New: CandidateQualityElection
Date Sat, 12 Feb 2005 18:34:46 GMT
   Date: 2005-02-12T10:34:46
   Editor: RobertBurrellDonkin
   Wiki: Jakarta Commons Wiki
   Page: CandidateQualityElection

   no comment

New Page:

= Candidate Quality Election =

The traditional release process in the Commons is as follows:

 * cut release candidate
 * announce release candidate on user and dev lists
 * wait a while to see if any issues are reported
 * VOTE on the release
 * cut release

This has many advantages. However, the actual release is never tested and the testing period
is short. Components with large numbers of downstream users may like to consider an alternative
system that encourages better testing of the actual release cut.

Candidate quality election follows a different pattern. A release is cut and announced as
a release candidate. It is then VOTE'd to alpha, beta and full release quantity. Each stage
is announced and users are encouraged to report any problems. If any issues emerge that must
be addressed, a new release is created and the cycle starts again. Developers are recommended
to VOTE +1 only if they have tested the release themselves.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message