--- Dirk Verbeeck <[EMAIL PROTECTED]> wrote: > David Graham wrote: > > > I don't think all commons > > components have to follow one release style. Maybe I just missed the > > documentation on this though. > > Here it is: > http://jakarta.apache.org/commons/releases/index.html
Yes, but those docs don't mandate that all commons components follow one build process. They merely document the process that most components follow. > > And I do think all commons components should follow the same > procedure. That is one of the the advantages of living under the > jakarta/commons umbrella (you don't have to define your own release > procedure, charter, ...) > > > I'm active on validator and I have no problem with the release. > > Personally, I prefer the commons release style over the httpd rules > but > > Rob volunteered his time to cut the release and it shouldn't get > bogged > > down by bureaucracy. Cutting a release is time consuming as it is. > > I think the minimal requirement is to call a VOTE (on the release) and > post the results to the pmc list. Even following the httpd rules you > have to VOTE on the stability of the build before releasing it into > the wild ;-) This was an alpha release so it didn't require a vote. This is one reason I prefer the current commons release process; it's much less confusing. All I'm saying is that we shouldn't waste Rob's time by rolling back a release he already cut. I'm fine with following the commons release process in the future. David > > -- Dirk > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
