Just to call this out, it's a common practice among several ASF projects to roll a release and then decide the quality. The notion is rather than roll 2.1.0-RC1, we roll 2.1.1 and then vote on whether the quality is alpha, beta, or GA. Sometimes a release will start off as a beta, and then graduate to GA. A huge benefit is that work can continue on 2.1.2, regardless of what happens to 2.1.1. Apache HTTPD uses this approach, as does Tomcat, Struts, and many others.
Of course, the foundation doesn't dictate a release scheme (only that the package meets legal standards), and Click is free to use whatever scheme works best for the PMC. -Ted. On Wed, Jul 1, 2009 at 2:02 PM, Bob Schellink<[email protected]> wrote: > Normally I'd say yes, however since the process of pushing out a release is > quite involved, I'd suggest we release RC1 if another binding vote is cast > (we only have 2 binding votes currently). > > If no other vote is forthcoming we can cut another RC1 when CLK-564 is > resolved. > > Also there is no reason why we cannot cut RC2 if needed. > > My 2c. > > bob > > > Malcolm Edgar wrote: >> >> Hi All, >> >> I would like to propose delaying the Click 2.1.0-RC1 to incorporate >> feedback raised about: >> * click-examples >> * community documentation >> * source attribution >> * GAE, Weblogic, WebSphere support >> https://issues.apache.org/jira/browse/CLK-564 >> >> I think this will make for a more solid RC1 apache release and put us >> in a better position for 2.1.0 final. >> >> regards Malcolm Edgar >> >> On Thu, Jun 18, 2009 at 2:25 AM, Bob Schellink<[email protected]> wrote: >>> >>> Hi all, >>> >>> I'd like to start a formal vote on releasing Click 2.1.0-RC1. >>> >>> SVN Tag: >>> >>> http://svn.apache.org/repos/asf/incubator/click/tags/click-2.1.0-RC1-take1/ >>> M2: http://people.apache.org/~sabob/click/click/2.1.0-RC1/maven2/ >>> Dist: http://people.apache.org/~sabob/click/click/2.1.0-RC1/dist/ >>> >>> The vote lasts 72 hours. >>> >>> Here is my +1. >>> >>> kind regards >>> >>> bob >>> >>> >> > >
