Right. And my point is, using the release process as the primary QA driver makes a lot of extra work for you. It's just messy to be getting bug reports and deciding what to do about them off of a vote thread.
On Tue, Jul 5, 2011 at 9:12 AM, Mohammad Nour El-Din <[email protected]> wrote: > +1 > > More specifically we are still getting used to the release process. > > On Tue, Jul 5, 2011 at 2:39 PM, Benson Margulies <[email protected]> > wrote: >> Might I suggest some sort of informal testing process *before* you >> call a vote? Go ahead, if you like, and stage XXX-RC-1 to nexus, but >> don't call a vote. Get people to test it and find problems like broken >> links and missing notices. When it all looks clean, just drop the >> staged repo, and run the release with the actual release version. Then >> your votes can look like 95% of all the other votes at apache; a >> pretty rapid verification process. >> > > > > -- > Thanks > - Mohammad Nour > Author of (WebSphere Application Server Community Edition 2.0 User Guide) > http://www.redbooks.ibm.com/abstracts/sg247585.html > - LinkedIn: http://www.linkedin.com/in/mnour > - Blog: http://tadabborat.blogspot.com > ---- > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein > > "Writing clean code is what you must do in order to call yourself a > professional. There is no reasonable excuse for doing anything less > than your best." > - Clean Code: A Handbook of Agile Software Craftsmanship > > "Stay hungry, stay foolish." > - Steve Jobs >
