On Tue, Nov 30, 2010 at 12:25 AM, Michael Glavassevich <[email protected]> wrote: > Hi Hiranya, > > Hiranya Jayathilaka <[email protected]> wrote on 11/29/2010 01:28:01 PM: > >> Hi Michae;, >> >> On Mon, Nov 29, 2010 at 11:29 AM, Michael Glavassevich >> <[email protected]> wrote: >> > Hi Hiranya, >> > >> > Hiranya Jayathilaka <[email protected]> wrote on 11/29/2010 12:05:33 >> > AM: >> > >> >> Hi Michael, >> >> >> >> Is our release process documented somewhere? >> > >> > It could do with some improvements (some of the details are out-of-date >> > / >> > missing since it was written long ago) but it's documented here [1]. >> > Voting >> > on signed packages is an ASF requirement and needs to occur beforestep 8 >> > in >> > this process. >> >> Thanks for the info >> >> > >> >> I'm just curious to know why we don't branch out of the trunk when >> >> doing a release. >> > >> > 2.11.0 was tagged on Friday. Any commits going on the trunk (or the XML >> > Schema 1.1 development branch) at this point would be for a follow-on >> > release. We've never made any other "maintenance" branches because >> > there's >> > never been a need for one. We've always just moved forward. >> >> For this to work properly, shouldn't we consider the trunk to be >> 'frozen' during a release cycle? > > It generally has been. Have never had to announce a code freeze because the > committers on previous releases have known to hold off on making changes in > this relatively short (critical) period around a release. Seems like common > sense to me, but perhaps we should start formally declaring one as > (relatively) newer contributors to the project may not recognize that.
+1 I think a small notice saying "please consider the trunk to be frozen for all development activities except for the features/fixes intended for the upcoming release" will be greatly helpful :) Thanks, Hiranya > >> Thanks, >> Hiranya >> >> > >> >> Thanks, >> >> Hiranya >> > >> > ... >> > >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> > >> > Thanks. >> > >> > [1] http://xerces.apache.org/xerces2-j/faq-contributing.html#faq-2 >> > >> > Michael Glavassevich >> > XML Parser Development >> > IBM Toronto Lab >> > E-mail: [email protected] >> > E-mail: [email protected] >> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
