You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2009/03/20 16:13:42 UTC
Subversion 1.6.0 Released
I'm happy to announce the public release of Subversion 1.6.0. Culminating
over 9 months of development effort, this is the best release of Subversion
yet, and delivers powerful features for both the client and server, including:
* Better filesystem storage mechanisms
* Authentication data handling improvements
* Early support for tree conflict detection
* ...and many more.
For full details, see the Subversion 1.6 Release Notes:
http://subversion.tigris.org/svn_1.6_releasenotes.html
Subversion 1.6.0 is immediately available from:
http://subversion.tigris.org/downloads/subversion-1.6.0.tar.bz2
http://subversion.tigris.org/downloads/subversion-1.6.0.tar.gz
http://subversion.tigris.org/downloads/subversion-1.6.0.zip
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.tar.bz2
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.tar.gz
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.zip
The MD5 checksums are:
db9f19671c1f5286be3a930c0a7d18f3 subversion-1.6.0.tar.bz2
b74985c9191d4a652a9f618a06171880 subversion-1.6.0.tar.gz
eff5b8615f1b292f69418dc00ead6809 subversion-1.6.0.zip
568b7b4ee3e2633c34510b02e6cea2cb subversion-deps-1.6.0.tar.bz2
df76f51a930c256c31d6ccd15879d761 subversion-deps-1.6.0.tar.gz
38510866180107de0290364f54d8690b subversion-deps-1.6.0.zip
The SHA1 checksums are:
a8088dd170ea38f6d175c6b009352922bc808013 subversion-1.6.0.tar.bz2
112fede653403da88e9b6488500934fa90dd4970 subversion-1.6.0.tar.gz
044a2423b5844e4299c3f46027a027e4af7d1f30 subversion-1.6.0.zip
9ad73768b839b84974099bed9233a8f1ad89771d subversion-deps-1.6.0.tar.bz2
f24dbc62ff7648d312ee1258ab39eb69b430f8c2 subversion-deps-1.6.0.tar.gz
74d7ce4c7a62d5aed19f42403057d5f8185ab05e subversion-deps-1.6.0.zip
PGP Signatures are available at:
http://subversion.tigris.org/downloads/subversion-1.6.0.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-1.6.0.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-1.6.0.zip.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0.zip.asc
For this release, the following people have provided PGP signatures:
C. Michael Pilato [1024D/1706FD6E] with fingerprint:
20BF 14DC F02F 2730 7EA4 C7BB A241 06A9 1706 FD6E
Paul T. Burba [1024D/53FCDC55] with fingerprint:
E630 CF54 792C F913 B13C 32C5 D916 8930 53FC DC55
Karl Fogel [1024D/DB00A248] with fingerprint:
B77E 8FB2 112F 9637 2E3E 3F08 BC9D BB13 DB00 A248
Bert Huijben [1024D/9821F7B2] with fingerprint:
2017 F51A 2572 0E78 8827 5329 FCFD 6305 9821 F7B2
Hyrum K. Wright [1024D/4E24517C] with fingerprint:
3324 80DA 0F8C A37D AEE6 D084 0B03 AE6E 4E24 517C
Mark Phippard [1024D/035A96A9] with fingerprint:
D315 89DB E1C1 E9BA D218 39FD 265D F8A0 035A 96A9
Kamesh Jayachandran [1024D/ED184C2C] with fingerprint:
3E5B 5C1D 1CA6 A611 2787 9B4B DD61 EFC8 ED18 4C2C
Release notes for the 1.6.x release series may be found at:
http://subversion.tigris.org/svn_1.6_releasenotes.html
You can find the list of changes between 1.6.0 and earlier versions at:
http://svn.collab.net/repos/svn/tags/1.6.0/CHANGES
Questions, comments, and bug reports to users@subversion.tigris.org.
Thanks,
- The Subversion Team
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1365516
Re: Subversion 1.6.0 Released
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Mar 20, 2009, at 11:50 AM, Arkadiusz Miskiewicz wrote:
> On Friday 20 of March 2009, Hyrum K. Wright wrote:
>
>> http://subversion.tigris.org/svn_1.6_releasenotes.html
>
> Bunch of unfilled data, "XXX" marks etc... is this some old version?
Yes, and no. The cron job that updates the website hasn't yet fired,
so the website does not yet reflect the 1.6.0 release.
However, we still have a few "missing" sections in the release notes,
and some of those XXX marks are legitimate TODOs for the developers to
either remove the section or fill in the missing data. Hopefully that
will happen soon.
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1365823
Re: Subversion 1.6.0 Released
Posted by Arkadiusz Miskiewicz <ar...@maven.pl>.
On Friday 20 of March 2009, Hyrum K. Wright wrote:
> http://subversion.tigris.org/svn_1.6_releasenotes.html
Bunch of unfilled data, "XXX" marks etc... is this some old version?
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
Re: Forcing the clients to upgrade to 1.5 or 1.6? Should we have
"svn:minclientversion" property?
Posted by Ben Collins-Sussman <su...@red-bean.com>.
Also described here:
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1397337
RE: Forcing the clients to upgrade to 1.5 or 1.6? Should we have
"svn:minclientversion" property?
Posted by Geoff Rowell <ge...@gmail.com>.
Aleksey Nogin [mailto:anogin@hrl.com] wrote:
> When 1.5.0 was released, I realized that I would not be able to use the
> new svn:externals syntax until I have some way of making sure the
> connecting clients are all at least version 1.5. Now that 1.6.0 adds
> support for file externals I expect a similar problem.
>
> Unfortunately, subversion does not have (AFAIK) any mechanisms to
> explicitly tell the clients to upgrade. An 1.4 client encountering an
> svn:externals in 1.5 format would give an very unhelpful error message
> that would be completely baffling to a user who have not yet heard about
> the new 1.5 svn:externals format.
>
Hi Aleksey,
Look at the new "capabilities" input to the server's "start-commit" hook. If
the client-provided value doesn't include "mergeinfo", you know it's a
pre-1.5 client.
-Geoff
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1393264
Forcing the clients to upgrade to 1.5 or 1.6? Should we have
"svn:minclientversion" property?
Posted by Aleksey Nogin <an...@hrl.com>.
When 1.5.0 was released, I realized that I would not be able to use the
new svn:externals syntax until I have some way of making sure the
connecting clients are all at least version 1.5. Now that 1.6.0 adds
support for file externals I expect a similar problem.
Unfortunately, subversion does not have (AFAIK) any mechanisms to
explicitly tell the clients to upgrade. An 1.4 client encountering an
svn:externals in 1.5 format would give an very unhelpful error message
that would be completely baffling to a user who have not yet heard about
the new 1.5 svn:externals format.
IMHO subversion needs two separate mechanisms for forcing upgrades:
1. A global per-repository "minimal client version" set by
administrator. E.g. for svnserve - when a clients connects to a
repository, svnserve would produce some sort of a "you must upgrade"
error message if the client's version is too old. It would be nice if
this could be added in a way that can distinguish between previous
clients (e.g. between 1.4 and 1.5), but even if a client
self-identification mechanism needs to be added for this, it would still
be very valuable going forward.
2. A per-directory mechanism accessible by repository users. The most
obvious would be to add a new property - e.g. something like
"svn:minclientversion". *If* such property had already existed and was
understood by previous subversion clients, I could set
"svn:minclientversion" to 1.5 simultaneously with adding 1.5-formatted
svn:externals and thus make sure the old clients would give a meaningful
"you client is too old" error instead of a "weird" error about and
unexpected relative path. Obviously, adding support for such property
would not help with incompatibilities introduced in 1.5 and 1.6, but at
least it would help with any future incompatibilities. In addition,
future clients may be changed to automatically bump the
"svn:minclientversion" whenever the user does something that would
require a recent client to correctly access.
What do people think?
Aleksey
--
Aleksey Nogin, Research Scientist
Advanced Technologies Department, Information & System Sciences Lab
HRL Laboratories, LLC, Malibu, CA
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1390623