Don, >> Then, once the release is out, people nitpick through it finding >> issues to shoot it down (and yes, a beta is as good as a killed >> release because it doesn't get out to the users in an public, >> accessible location).
I must be one of the folk guilty of nit-picking :) But honestly, I thought I found some legtimate issues, but that's only because the release managers asked people to find issues with it. I mean, the nit-picking has to be after a release because who wants to test something that's constantly in-flux? There needs to be a pretty stable baseline, and that's what I believe the release is for. So many changes go in and out of SVN, it's difficult to tell when things are published or not (like the site) in a distribution. But as for the problem with 1.3.4, it is "bigger" than Struts itself: it's an infrastructure issue, so I am told. Therefore, let's call this an exception. -- Paul --- Don Brown <[EMAIL PROTECTED]> wrote: > Craig McClanahan wrote: > > However, I would be unhappy with > > all of us other committers if we stopped testing 1.3.4 at all, until > > 1.3.5became available, and we surface yet another two line change next > > week. > This is exactly why I think this release process, or least least the > Struts PMC implementation of it, is broken. A few Struts committers > work their butts off to push out a release, clearing all known issues > and repeatedly asking for help but getting none. Then, once the release > is out, people nitpick through it finding issues to shoot it down (and > yes, a beta is as good as a killed release because it doesn't get out to > the users in an public, accessible location). Ok, we go back, fix the > issues, and roll another release, only to have the same process happen > again and again. > > Honestly, this is very discouraging and kills any momentum we get. > Personally, I give up. I previously believed Struts moved so slowly > because of a lack of effort, but I'm wondering if the problem isn't more > profound. If, in six months with 100% dedicated committers willing to > do whatever it takes and a codebase that is stable and proven, we can't > push out a GA release, we have a serious problem. > > Don > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
