On 3/19/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Something being a good idea and being "required ASF policy" are really very different things. The suffering is in the implication that I'm not already being careful.
So you've never made a mistake in your life? And you're willing to bet a law suit on continuing to never make a mistake? That we're not all supposed to be slightly better than
average developers with the apache branding and all. The fact that it's ok to send me emails telling me I'm part of a "problem project" because I haven't followed some new guidelines put in place because of other peoples mistakes - mistakes I haven't even made ....is really just insulting and annoying. I wonder how often these kinds of emails come out on the google code or sourceforge lists? :/
Those sites provide infrastructure, but absolutely no legal protection. -- Martin Cooper On 3/19/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
<snipped> > There are all sorts of things that can go wrong when cutting a release > - an example the other day - Tomcat 5.5.23 had/has a problem because > the RM didn't have a jar in his local environment - its not a > guarantee I know (Tomcat produce artifacts to vote on before release!) > - but the more pairs of eyes checking out the distro before it goes > out has got to be a good thing. Its not about incompetance, just > catching mistakes before rather than after. I also don't get your > "suffering" point - most projects can produce a RC quickly - Tag & > Build - doesn't take long - so where is the suffering in doing that > before calling a vote? > > Niall -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
