Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 4:29:31 PM >>> * "Brad Nicholes" <[EMAIL PROTECTED]> wrote: >During ApacheCon several httpd PMC members got together to discuss > current issues with the httpd project and to try to find better ways to > manage the project.

Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 4:46:45 PM >>> On 17.11.2004, at 00:30, Cliff Woolley wrote: > On Tue, 16 Nov 2004, Justin Erenkrantz wrote: > >> I think this is a bad idea and would make stable turn into CTR. And, >> that, I >> believe jeopardizes the overa

Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 5:21:28 PM >>> +1 Lazy consensus applied in this way will help the less popular parts of our codebase to continue to evolve and stabilize. Up to this point, only the most popular patches have been getting enough attention to rec

Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to the dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 5:48:15 PM >>> >If there are a lack of votes for backport, then I believe that is a sign that >there is not a healthy enough community of people who are able to review the >code. I'd like to ensure that we don't create 'isla

Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 6:00:16 PM >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 it might open up a couple of bugs/regressions, but it will certainly mean more fixes going in On 17/11/2004, at 10:08 AM, Brad Nicholes wrote: >During Apache

Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-16 Thread Brad Nicholes
moving to dev@ list >>> [EMAIL PROTECTED] Tuesday, November 16, 2004 6:04:08 PM >>> This proposal is in addition to the proposal on the dev list. Once the code converts from CTR to RTC in a stable branch, then we need a way to make sure that overhead doesn't stifle ennovation. The fact is t

Re: Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-18 Thread Astrid Keßler
[EMAIL PROTECTED] Tuesday, November 16, 2004 4:29:31 PM >>> > * "Brad Nicholes" <[EMAIL PROTECTED]> wrote: >>During ApacheCon several httpd PMC members got together to discuss >> current issues with the httpd project and to try to find better ways to >> manage the project. One of the iss

Re: Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-18 Thread Justin Erenkrantz
--On Friday, November 19, 2004 12:41 AM +0100 Astrid Keßler <[EMAIL PROTECTED]> wrote: Additionally, let's do 2.1 tarballs to bring the current development branch to a wider group of devs and testers. I plan to roll 2.1.1 as soon as the final import finishes: roughly a few hours from now. ;-)

Re: Fwd: Re: [PROPOSAL-VOTE] Adopt lazy consensus for backports...

2004-11-19 Thread William A. Rowe, Jr.
At 05:41 PM 11/18/2004, Astrid Keßler wrote: >> IMHO a better way bring the development further is the suggestion on the dev >> list. *absolute* feature freeze on stable branches (except 1.3?), bug fixes >> only. Though it would need some time to establish the trust of the community >> in so much