>>> On 4/12/2008 at 11:20 AM, in message <[EMAIL PROTECTED]>, Paul Querna <[EMAIL PROTECTED]> wrote: > This is something I have been thinking about for awhile, and discussed > with a few other http server people before. > > I think that for the 'stable' branch, we should move to time based releases. > > My proposal is for every 2 months, we do a release of the main stable > branch, which at this time is 2.2.x. > > Security Issues of great importance of course would trigger an immediate > release. Depending on the nearness to a scheduled release, we may or > may not scrap the next time based release. >
I guess I am not sure what setting a schedule is trying to accomplish. Can't you do this already? If somebody wants to release every 2 months, that person can call for the release and be the RM every two months. In other words, as long as there is somebody willing to do the work, then the work will happen. If a release isn't required, ie. no real appreciable improvement since the previous release, then why require everyone to mobilize for very little gain. I guess I am looking for the problem that a hard schedule resolves when we can already release as early or as often as desired. Brad
