Re: [VOTE] Release Candidate JMeter 2.3 RC1 - abandoned
jean-frederic clere <[email protected]>
| Newsgroups | gmane.comp.jakarta.general |
|---|---|
| Message-ID | <[email protected]> |
Dion Gillard wrote: >> From looking at Struts SVN, I'm guessing that they're built and then >> tagged > from a revision of trunk and then that tag is voted on for quality. > > Maybe one of the Struts/Tomcat committers can explain how they do it? In Tomcat the committers agree on a release date the corresponding code is tagged binaries and source packages are prepared and made available for download. People are asked to vote: For example, the x.y.z tag is: [ ] Broken [ ] Alpha [ ] Beta [ ] Stable After the vote the release is announced. (Normally Stable is what we want to reach and announce). Cheers Jean-Frederic Ted, > Don? > > On 7/9/07, sebb <[email protected]> wrote: >> >> On 09/07/07, Dion Gillard <[email protected]> wrote: >> > sebb, >> > >> > one of the things I find useful about the build process that httpd, >> Struts, >> > Tomcat etc use is that it means anyone can do a build and then call for >> a >> > vote on it's quality. >> > >> > If this process is streamlined enough, it means feedback can be >> extracted >> > from people more often and issues discovered earlier. >> > >> > I know this isn't how things are done ATM with jakarta, but it's worth >> > thinking about. >> >> I have been making regular nightly builds available, however it was >> only when I created a formal build and called for a vote that various >> issues surfaced. >> >> So yes, it could be useful in future. >> >> Do these quality check builds have to be tagged in SVN? >> Or can they just be built from the current code line? >> >> > On 7/9/07, sebb <[email protected]> wrote: >> > > >> > > On 04/07/07, sebb <[email protected]> wrote: >> > > > I've created JMeter 2.3 RC1 in the directory: >> > > > >> > > > http://people.apache.org/~sebb/jmeter-2.3/dist >> > > > >> > > > Site/Docs are here: >> > > > http://people.apache.org/~sebb/jmeter-2.3/site >> > > > >> > > > All feedback welcome. >> > > > >> > > > [ ]+1 - the release candidate looks OK, proceed with full release >> > > > [ ]-1 - there is a problem (please indicate what it is) >> > > >> > > Various problems have been found in the release, so I won't be >> > > proceeding with it. >> > > >> > > Thanks for all the feedback so far, which has been very useful. >> > > >> > > I have been able to fix most of the reported problems, but there are >> > > still some outstanding. >> > > >> > > > sebb AT apache DOT org >> > > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > >> > >> > -- >> > dIon Gillard >> > Rule #131 of Acquisition: Information is Profit. >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > >