Re: Release targets and timeline for 1.4?

Lieven Govaerts wrote:
>
> I expect this will lead to svn admins avoiding the new release altogether
> until the first set of fixes comes out.
>

We already do this. We have multiple SVN repos, linked to trac
projects. Trying to update the server also means updating trac to use
the new python bindings etc which ends up not being a 2 minute job just
to install the new version of svn and re-start apache.

It isn't overly difficult, but a large enough job that if something went
wrong and we had to go back to the previous version, it would be a real
headache.

We also haven't been upgrading our servers until a .1 release has been
done. 1.2.0 had a client issue where status -u wouldn't work with a
1.1.x server and 1.3.0 has problems with SSPI (both authentication and
performance, according to TSVN folk) which were looking to move to.
These sort of things, while not major, aren't what we want to hit when
doing an upgrade.

Cheers

Russell

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 09:54:34 2006