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

1.8.0 release timing

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 30 May 2013 09:00:01 -0400

I've been working with the ASF's marketing team on the official Apache
Subversion 1.8.0 press release, and we're trying to get a feel for the
timing of the final release (and by extension, the press announcement).

This community posted 1.8.0-rc2 on Tuesday, May 14, with verification and
public release completing on Thursday, May 16. While it's not precisely
spelled out in the Community Guide which of those two dates starts the soak
period, I'm going to assume it's the latter. The point of the soak period
is to expose the code to the public for a period of time and arguably the
code isn't fully exposed until the release is verified and announced. But
I'm happy to entertain alternative viewpoints here.

I am unaware of any soak-restart-worthy changes made to the branch since
that time. As such, it would seem that if we were trying to minimize the
release schedule, we would need to release 1.8.0-rc3 -- final in all but
name -- on Thursday, June 6. The final release then falls a week later on
Thursday, June 13.

I anticipate the signing/release of the final tarball to go extremely
quickly, especially for those who sign the rc3 tarball. (Yup, checksums
match, diffs vs. rc3 are as expected and don't effect codepaths ... ship it!)

That's sorta the minimum-time scenario, of course. Keeping in mind that
we'll have devs in transit between ${HOME} and Berlin at a pretty critical
time during this soak period, what, if any, plans do we *actually* have
regarding the timeline of this release?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2013-05-30 15:00:43 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.