Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <46B46AA8.3040801@apache.org>
References: <5EC0435F-DDF3-4CC2-B0FA-F4AA5B28957D@jaguNET.com>
 <46B46AA8.3040801@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <60D2FE1C-7CCD-4F9B-B5E5-8781EC402D4B@jaguNET.com>
Content-Transfer-Encoding: 7bit
From: Jim Jagielski <jim@jaguNET.com>
Subject: Re: T&R schedule
Date: Sat, 4 Aug 2007 10:42:15 -0400
To: dev@httpd.apache.org


On Aug 4, 2007, at 8:01 AM, Ruediger Pluem wrote:

>
>
> On 08/03/2007 06:21 PM, Jim Jagielski wrote:
>> Lets shoot for a T&R of 1.3, 2.0 and 2.2 on Aug 10th... That
>> means a possible release on the 13th. That way, admins
>> aren't compelled to upgrade before/during the weekend (other-
>> wise, T&R on the 8th and release on the 10th would make
>> sense)
>
> +1 in general, but I think the timing of T&R should be independent
> from admins needs. It should be more driven by the ability of
> people to test the RC.

Actually, it's both, with the pref, of course, given
to actual testing. However, coming from the fact that,
from the beginning, we developers were also users (and
admins), we maintain an affinity for the troubles and
turmoils of being an admin, and try to avoid doing
releases right before the weekend or holidays, if
we can help it.