[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PROPOSAL] - maintain projected release date for 1.7

From: Hyrum K Wright <hyrum.wright_at_wandisco.com>
Date: Wed, 31 Aug 2011 09:17:28 -0500

On Wed, Aug 31, 2011 at 8:57 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Wed, Aug 17, 2011 at 10:42 AM, Hyrum K Wright <hyrum.wright_at_wandisco.com>
> wrote:
>>
>> On Wed, Aug 17, 2011 at 9:19 AM, Mark Phippard <markphip_at_gmail.com> wrote:
>> > I would like to see us maintain a projected release date for 1.7 once we
>> > have moved to the RC phase.  Most likely place to put it would be here:
>> > http://subversion.apache.org/roadmap.html
>> > I think including this date in the RC announcement would make the
>> > announcement stronger and encourage testing, although I am fine with
>> > just
>> > maintaining it on our dev@ list and website.
>> > We have a good idea when the release date will be, based on our defined
>> > policies.  I think publicizing when we anticipate rolling the final
>> > release
>> > tarball and likely release the signed version will simply eliminate
>> > confusion by letting everyone know in advance when these events are
>> > going to
>> > happen.  This also makes it easier for our downstream ecosystem, such as
>> > TortoiseSVN, Subclipse, AnkhSVN etc. to know when to expect the release
>> > so
>> > that they can better plan their own releases.
>> > If we need to create a new RC and restart the soak period, then we can
>> > just
>> > update the date to reflect this but at least we can all be on the same
>> > page
>> > about it and give our downstream a proper heads-up on the change and
>> > what
>> > that means for the new date.
>> > Based on my math, if we roll RC1 this week and release on Monday, then
>> > add 4
>> > weeks for the soak and we have Sept. 19.  Assuming we roll final tarball
>> > on
>> > Weds (Sept 21) we would then expect to release on Monday Sept 26.
>>
>> IIRC, we can roll the final before the end of the soak, so as to
>> release when the 4-week soak is up.
>>
>> but +1 on the general idea of being more communicative to our users
>> and publicizing our anticipated release dates.
>
> Are you planning to publish a projected a release date with the RC
> announcement?

My plan was to announce the beginning of the soak period, and notify
folks of the anticipated release at the end of the soak with the RC
announcement (which I'm in the process of writing).

> What is the projected date?  Would we try to release 4 weeks from today
> (Sept 28th) or would we plan on publishing the tarball for signatures on
> that date with the release sometime the following week?

"Last week of Sept / first week of Oct." was my general gut feeling.
I wasn't planning on a specific date (I can't even pinpoint a specific
date for a candidate tarball a few days out).

> If we are going to release on Sept 28th, I would assume you plan to roll the
> final tarball around Sept 21/22 ?

Probably late 22nd. I'll be traveling most of the 23rd.

The way it will go down is thus[1]:
 * If people feel we've got sufficient reason, I'll create the final
RC (call it rcN) from magic revision rM.
 * People test and sign as usual, and we release it as rcN.
 * Assuming no complaints, a couple of days before the final release
I'll roll 1.7.0 from rM.
 * Because 1.7.0 is from the same magic rev, people can just verify
that fact and resign, since they have already tested.
 * Release!

There will be a little bit of delay by the mirroring system, but Mike
and I were discussing the possibility of releasing before the mirrors
have caught up and just warning our users of this fact in the release
announcement. That would compress things a bit, but I'm generally
indifferent.

-Hyrum

[1] This is all documented here:
http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/
Received on 2011-08-31 16:18:00 CEST

This is an archived mail posted to the Subversion Dev mailing list.