incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: [PROPOSAL][VOTE] Subversion
Date Fri, 06 Nov 2009 18:43:08 GMT
On Thu, Nov 5, 2009 at 12:48, Martijn Dashorst
<> wrote:
> On Thu, Nov 5, 2009 at 5:20 PM, Greg Stein <> wrote:
>> I do not expect Subversion to make a release while in Incubation. Our
>> next big release is 1.7, and is expected in (hopefully?) Q1 next year.
>> There is a chance that we'd like to release 1.6.7 while we're
>> incubating. That can be a bridge to cross later.
> While I have great confidence in the ability of the subversion team to
> build quality and legally sound releases, I do think that doing one
> release inside the incubator would be prudent. If only to ensure due
> process. In my opinion getting a release vetted by the IPMC is one of
> the hardest things to accomplish and diversity aside the most
> important aspect of a successful incubation.

You can read about Subversion's release process here:

I will posit that it uses a process that exceeds that performed by
most Apache projects. I hear what you're saying, but will point out
that svn has SEVEN Members of the ASF(*) on its equivalent of a PMC.
There is more than ample experience with how the ASF produces

But with all that said, how about we do this: we'll do a 1.6.7 release
from the 1.6.x branch after we do the code import. That release will
be performed by svncorp (we don't want to touch every file on that
branch to relicense it, and to switch file headers). The release
process can be followed/tracked by the Incubator PMC. I'll make sure
to relay pointers to all relevant threads as the release is performed.

Here are some relevant mail messages from the 1.6.6 release process,
so you'll know what to expect for 1.6.7:

Initial announcement for release-process-start (Sep 28):

Call for testing/signatures of the release tarball (Oct 15):

Release announcement (Oct 21):

I believe the primary difference will be installing the release
tarball onto and its mirroring system (in addition to Third parties who produce precompiled binaries
may continue to do so, but can fetch their tarballs from the new

Note: we may want to load all the old releases onto Infra is fine with this, but that decision hasn't
been made by the project yet.

After the code import, we'll switch trunk over to the ASF standard
header (our files have the same header, but s/ASF/svncorp/). The trunk
will then be ready for 1.7 release as an ASF-branded project.

Any thoughts or concerns?


(*) the ASF Members are: gstein, jorton, fitz, jerenkrantz, striker, rooneg, dlr

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message