On Tue, Aug 23, 2011 at 4:07 AM, Bert Huijben <bert_at_qqmail.nl> wrote:
>> -----Original Message-----
>> From: Hyrum K Wright [mailto:hyrum.wright_at_wandisco.com]
>> Sent: vrijdag 19 augustus 2011 20:24
>> To: Subversion Development
>> Subject: 1.7.0-rc1 up for testing / signing
>> Here it is: the first Release Candidate for Subversion 1.7.0. You can
>> fetch the proposed tarballs from here:
>> The magic rev is r1159696; please post signatures at the normal location:
>> This is a release candidate, meaning if all goes well it (or something
>> very much like it) will become the final release. Please test this as
>> if it were the final release, understanding that there will be bugs in
>> any software we ship. <insert lecture about perfect being enemy of
>> the good here>
> +1 to release as 1.7.0-RC1 as all tests pass for me.
> -0 to release as Subversion 1.7.0
> I don't think we tried hard enough to clear STATUS to make this a valid 1.7.0 for me.
> There are still a few items that should have been resolved.
> The only reason to make this a 1.7.0 would be that we assume that all users just wait until 1.7.1 anyway, and I don't want to encourage users to do that.
To paraphrase a private mail I sent around yesterday: "We encourage
people that are testing it to do so as if it was the final release.
They'll either be testing it as rc1 or as the final, and the former is
preferable to both us and them."
Of course, if we *do* find and fix bugs, 1.7.0-rc1 doesn't have to
become the final release; we can fix the bugs prior to that happening.
In any case the release plan (and my plan) is that we roll a final RC
a few days before the final release to pick up any remaining bug fixes
which have been merged to the branch. I'm not even opposed to doing
an rc2 in a couple of weeks at the half-way point of the soak.
uberSVN: Apache Subversion Made Easy
Received on 2011-08-23 14:50:03 CEST