On 11/28/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On 11/28/05, Sean Schofield <[EMAIL PROTECTED]> wrote: <snip/> > > > > A few questions. For these interim builds that don't get released > > officially. I assume these builds aren't in the apache archive or > > Maven repository right? You just make them in the nightly dir or > > something for people to evaluate? Also, for bug reporting do you > > recommend a verison number for each interim release? > > Ah, well, it's not an "interim" release. It's a release that we have > graded test, Alpha, Beta, or GA. > > Initially, we make the build available in a committer's home directory > or in the usual download directory, but we do not announce it the user > list or submit it for mirroring until there is a quality vote. The > ones that make it past the test-build stage go into the archive, just > like most betas and rcs. > > * http://archive.apache.org/dist/struts/ > <snap/>
Since I couldn't find the relevant thread(s) in the archives - What is the intent behind not announcing on the user list? Avoiding potential for confusion? If one goes by the premise that users are (a very important part of) the development community, and arguably the only "true" evaluators of the quality of your code, it would suggest that a heads up on the user list *before* an upcoming quality vote is quite appropriate? Sure, it might generate some amount of noise, but some feedback will inevitably be useful and no one -- not even HTTPD -- can claim that cutting a release / test build is unobtrusive for the RM ;-) For example, the most recent RC in Commons is receiving feedback from users (even *potential* users, like me). Ofcourse, this is orthogonal to RC vs grade vote, it is not my intent to revisit that. -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
