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

Re: The svn 1.2 release.

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-03-31 23:35:35 CEST

Ben Collins-Sussman wrote:

> OK, we're essentially at the end of the road for 1.2.
> * Locking feature is merged and tested
> * APIs are nearly done being cleaned up
> * last minute bugs are being fixed
> * issuetracker is being swept
> * I'm almost done with CHANGES and release-notes
> There are still some loose ends to tie up, but after some discussion
> with Ben Reser and Justin Erenkrantz, we'd like to do the branch and
> 1.2-rc1 tarball on Monday, starting around 10am Pacific time.
> So, there are two reasons for this email:
> First, this is an official "last call" for patches, tweaks.

Ah, time to get the Windows password encrypting simple provider into the

> Second, acting as co-RM's for this release, Ben and Justin would like
> to use 1.2 as an opportunity for making some tweaks to our release
> procedure:
> 1. Switch to libtool 1.5.10 in our tarball. Apparently this has
> been working well for the httpd project, and solves a number problems
> people have complained about. (Justin has details.)

Heh, couldn't care less... :-)

> 2. Require more formalized testing of the tarball. Just like the
> httpd release process, require three committers to officially "+1"
> (and gpg-sign) the tarball before release.

+1. It's Time.

> Comments welcome.

I don't know what's happening with the SWIG bindings in the Windows
build. Specifically, I suspect we don't support swig-1.3.23 (or whatever
it is) on Windows yet, and I think we should.

Would such build changes fall under the "bindings changes are allowed" rule?

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 31 23:36:58 2005

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.