You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Reser <br...@apache.org> on 2015/03/19 04:57:45 UTC
Apache Subversion 1.9.0-beta1 released
I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#pre-releases
The SHA1 checksums are:
cbc62b682e69254f57e40da316ebb7fcf998f56e subversion-1.9.0-beta1.tar.bz2
57142f460c51f334429569757974006f275240e8 subversion-1.9.0-beta1.tar.gz
66d84c7818d05141e795ed090dba3044c880f6ca subversion-1.9.0-beta1.zip
PGP Signatures are available at:
http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.bz2.asc
http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.gz.asc
http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.zip.asc
For this release, the following people have provided PGP signatures:
Ben Reser [4096R/16A0DE01] with fingerprint:
19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
Bert Huijben [4096R/CCC8E1DF] with fingerprint:
3D1D C66D 6D2E 0B90 3952 8138 C4A6 C625 CCC8 E1DF
Branko Čibej [4096R/A347943F] with fingerprint:
BA3C 15B1 337C F0FB 222B D41A 1BCA 6586 A347 943F
Julian Foad [4096R/4EECC493] with fingerprint:
6011 63CF 9D49 9FD7 18CF 582D 1FB0 64B8 4EEC C493
Philip Martin [2048R/ED1A599C] with fingerprint:
A844 790F B574 3606 EE95 9207 76D7 88E1 ED1A 599C
Stefan Fuhrmann [4096R/57921ACC] with fingerprint:
056F 8016 D9B8 7B1B DE41 7467 99EC 741B 5792 1ACC
This is a pre-release for what will eventually become Apache Subversion
1.9.0. It may contain known issues, a complete list of
1.9.0-blocking issues can be found here:
http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.9.0
A pre-release means the Subversion developers feel that this release
is ready for widespread testing by the community. There are known issues
(and unknown ones!), so please use it at your own risk, though we do
encourage people to test this release thoroughly. Of particular note, please
remember than persistent data, such as the working copy or repository
formats may change before the final release, and there may not be an
upgrade path from the pre-releases to the final.
As a note to operating system distro packagers: while we wish to have this
release candidate widely tested, we do not feel that it is ready for packaging
and providing to end-users through a distro package system. Packaging a
release candidate poses many problems, the biggest being that our policy lets
us break compatibility between the release candidate and the final release, if
we find something serious enough. Having many users depending on a release
candidate through their distro would cause no end of pain and frustration that
we do not want to have to deal with. However, if your distro has a branch that
is clearly labeled as containing experimental and often broken software, and
explicitly destined to consenting developers and integrators only, then we're
okay with packaging the release candidate there. Just don't let it near the
end users please.
Release notes for the 1.9.x release series may be found at:
http://subversion.apache.org/docs/release-notes/1.9.html
You can find the list of changes between 1.9.0-beta1 and earlier versions at:
http://svn.apache.org/repos/asf/subversion/tags/1.9.0-beta1/CHANGES
Questions, comments, and bug reports to users@subversion.apache.org.
Thanks,
- The Subversion Team
RE: Apache Subversion 1.9.0-beta1 released
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Ben Reser [mailto:breser@apache.org]
> Sent: donderdag 19 maart 2015 19:34
> To: Daniel Shahaf
> Cc: Subversion Development
> Subject: Re: Apache Subversion 1.9.0-beta1 released
>
> On 3/18/15 11:57 PM, Daniel Shahaf wrote:
> > That link isn't stable: issues disappear from it as soon as they are
> > merged to 1.9.x, so if we fix issue #4560 tomorrow it won't appear in
> > the link, even though it does affect 1.9.0-beta1.
> >
> > Next time, it would be better to explicitly list the known blocker
> > issues. (Unless we plan to introduce a 1.9.0-beta1 milestone.)
> >
> > For future reference, right now that link contains:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4560 (pin-externals
API
> semantics)
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4565 (prospective
blame)
> >
> > I'm not sure whether #4565 was fixed in beta1 or not. I'm not sure if
> > there are other formerly-1.9.0-blocker issues that have been fixed since
> > beta1 had been tagged and so are not currently in the linked buglist.
> >
> That's the output from release.py for write-announcement. I didn't think
any
> of the issues were big enough to specifically point out so I didn't edit
it
> this time. But I agree it's not a particularly useful link. On top of
your
> problem is the issue that we're not very good about using the issue
tracker on
> a regular basis.
I think we resolved issue 4565, before beta 1. (Not sure about that other
issue)
It provides several options and I haven't seen any discussion for that issue
on any of our channels.
Bert
Re: Apache Subversion 1.9.0-beta1 released
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Ben Reser wrote on Thu, Mar 19, 2015 at 11:33:54 -0700:
> On 3/18/15 11:57 PM, Daniel Shahaf wrote:
> > That link isn't stable: issues disappear from it as soon as they are
> > merged to 1.9.x, so if we fix issue #4560 tomorrow it won't appear in
> > the link, even though it does affect 1.9.0-beta1.
> >
> > Next time, it would be better to explicitly list the known blocker
> > issues. (Unless we plan to introduce a 1.9.0-beta1 milestone.)
> >
> > For future reference, right now that link contains:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4560 (pin-externals API semantics)
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4565 (prospective blame)
> >
> > I'm not sure whether #4565 was fixed in beta1 or not. I'm not sure if
> > there are other formerly-1.9.0-blocker issues that have been fixed since
> > beta1 had been tagged and so are not currently in the linked buglist.
> >
> That's the output from release.py for write-announcement. I didn't think any
> of the issues were big enough to specifically point out so I didn't edit it
> this time. But I agree it's not a particularly useful link.
Then perhaps something like this? It would require the RM to manually
fill in the known issues for each release, but I don't see an easy way
around that.
Index: rc-release-ann.ezt
===================================================================
--- rc-release-ann.ezt (revision 1667899)
+++ rc-release-ann.ezt (working copy)
@@ -17,10 +17,9 @@
[siginfo]
This is a pre-release for what will eventually become Apache Subversion
-[major-minor-patch]. It may contain known issues, a complete list of
-[major-minor-patch]-blocking issues can be found here:
+[major-minor-patch]. It contains the following known issues:
- http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=[major-minor-patch]
+* ...
A pre-release means the Subversion developers feel that this release
is ready for widespread testing by the community. There are known issues
The new text should of course be used only for alpha/beta and not for
release candidates, but ezt conditionals ([if ...]...[end]) could take
care of that.
> On top of your problem is the issue that we're not very good about
> using the issue tracker on a regular basis.
*nod*
Daniel
Re: Apache Subversion 1.9.0-beta1 released
Posted by Ben Reser <br...@apache.org>.
On 3/18/15 11:57 PM, Daniel Shahaf wrote:
> That link isn't stable: issues disappear from it as soon as they are
> merged to 1.9.x, so if we fix issue #4560 tomorrow it won't appear in
> the link, even though it does affect 1.9.0-beta1.
>
> Next time, it would be better to explicitly list the known blocker
> issues. (Unless we plan to introduce a 1.9.0-beta1 milestone.)
>
> For future reference, right now that link contains:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4560 (pin-externals API semantics)
> http://subversion.tigris.org/issues/show_bug.cgi?id=4565 (prospective blame)
>
> I'm not sure whether #4565 was fixed in beta1 or not. I'm not sure if
> there are other formerly-1.9.0-blocker issues that have been fixed since
> beta1 had been tagged and so are not currently in the linked buglist.
>
That's the output from release.py for write-announcement. I didn't think any
of the issues were big enough to specifically point out so I didn't edit it
this time. But I agree it's not a particularly useful link. On top of your
problem is the issue that we're not very good about using the issue tracker on
a regular basis.
Re: Apache Subversion 1.9.0-beta1 released
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
On Wed, Mar 18, 2015 at 08:57:45PM -0700, Ben Reser wrote:
> This is a pre-release for what will eventually become Apache Subversion
> 1.9.0. It may contain known issues, a complete list of
> 1.9.0-blocking issues can be found here:
>
>
> http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.9.0
That link isn't stable: issues disappear from it as soon as they are
merged to 1.9.x, so if we fix issue #4560 tomorrow it won't appear in
the link, even though it does affect 1.9.0-beta1.
Next time, it would be better to explicitly list the known blocker
issues. (Unless we plan to introduce a 1.9.0-beta1 milestone.)
For future reference, right now that link contains:
http://subversion.tigris.org/issues/show_bug.cgi?id=4560 (pin-externals API semantics)
http://subversion.tigris.org/issues/show_bug.cgi?id=4565 (prospective blame)
I'm not sure whether #4565 was fixed in beta1 or not. I'm not sure if
there are other formerly-1.9.0-blocker issues that have been fixed since
beta1 had been tagged and so are not currently in the linked buglist.
Cheers,
Daniel
RE: Apache Subversion 1.9.0-beta1 released
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Ben Reser [mailto:breser@apache.org]
> Sent: donderdag 19 maart 2015 04:58
> To: Subversion Development; users@subversion.apache.org;
> announce@subversion.apache.org; announce@apache.org
> Subject: Apache Subversion 1.9.0-beta1 released
>
> I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
> Please choose the mirror closest to you by visiting:
>
> http://subversion.apache.org/download/#pre-releases
For whoever is interested in testing this on Windows. The SlikSvn builds of 1.9.0-beta1 are now available as:
https://sliksvn.com/pub/Slik-Subversion-1.9.0-beta1-win32.msi (x86 version)
https://sliksvn.com/pub/Slik-Subversion-1.9.0-beta1-x64.msi (x86_x64 version)
(as usual full debug symbols are available in the https://sliksvn.com/pub/symbols/ directory)
Installing these miss will automatically upgrade your previous version of SlikSvn to this version.
To avoid an installer error on downgrading back to 1.8.x *) manually deinstall this version from the Software control panel, before (re)installing the older version.
Bert
*) The problem is just that setup fails because it can't install with a newer version installed.
Re: Apache Subversion 1.9.0-beta1 released
Posted by Branko Čibej <br...@wandisco.com>.
On 19.03.2015 04:57, Ben Reser wrote:
> I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
> Please choose the mirror closest to you by visiting:
>
> http://subversion.apache.org/download/#pre-releases
>
> The SHA1 checksums are:
>
> cbc62b682e69254f57e40da316ebb7fcf998f56e subversion-1.9.0-beta1.tar.bz2
> 57142f460c51f334429569757974006f275240e8 subversion-1.9.0-beta1.tar.gz
> 66d84c7818d05141e795ed090dba3044c880f6ca subversion-1.9.0-beta1.zip
>
> PGP Signatures are available at:
>
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.bz2.asc
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.gz.asc
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.zip.asc
>
> For this release, the following people have provided PGP signatures:
>
> Ben Reser [4096R/16A0DE01] with fingerprint:
> 19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
> Bert Huijben [4096R/CCC8E1DF] with fingerprint:
> 3D1D C66D 6D2E 0B90 3952 8138 C4A6 C625 CCC8 E1DF
> Branko Čibej [4096R/A347943F] with fingerprint:
> BA3C 15B1 337C F0FB 222B D41A 1BCA 6586 A347 943F
> Julian Foad [4096R/4EECC493] with fingerprint:
> 6011 63CF 9D49 9FD7 18CF 582D 1FB0 64B8 4EEC C493
> Philip Martin [2048R/ED1A599C] with fingerprint:
> A844 790F B574 3606 EE95 9207 76D7 88E1 ED1A 599C
> Stefan Fuhrmann [4096R/57921ACC] with fingerprint:
> 056F 8016 D9B8 7B1B DE41 7467 99EC 741B 5792 1ACC
>
> This is a pre-release for what will eventually become Apache Subversion
> 1.9.0. It may contain known issues, a complete list of
> 1.9.0-blocking issues can be found here:
>
>
> http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.9.0
>
> A pre-release means the Subversion developers feel that this release
> is ready for widespread testing by the community. There are known issues
> (and unknown ones!), so please use it at your own risk, though we do
> encourage people to test this release thoroughly. Of particular note, please
> remember than persistent data, such as the working copy or repository
> formats may change before the final release, and there may not be an
> upgrade path from the pre-releases to the final.
>
> As a note to operating system distro packagers: while we wish to have this
> release candidate widely tested, we do not feel that it is ready for packaging
> and providing to end-users through a distro package system. Packaging a
> release candidate poses many problems, the biggest being that our policy lets
> us break compatibility between the release candidate and the final release, if
> we find something serious enough. Having many users depending on a release
> candidate through their distro would cause no end of pain and frustration that
> we do not want to have to deal with. However, if your distro has a branch that
> is clearly labeled as containing experimental and often broken software, and
> explicitly destined to consenting developers and integrators only, then we're
> okay with packaging the release candidate there. Just don't let it near the
> end users please.
>
>
> Release notes for the 1.9.x release series may be found at:
>
> http://subversion.apache.org/docs/release-notes/1.9.html
>
> You can find the list of changes between 1.9.0-beta1 and earlier versions at:
>
> http://svn.apache.org/repos/asf/subversion/tags/1.9.0-beta1/CHANGES
>
> Questions, comments, and bug reports to users@subversion.apache.org.
>
> Thanks,
> - The Subversion Team
Users of Homebrew on Mac OS X can now install this version with
$ brew install subversion --devel
-- Brane
Re: Apache Subversion 1.9.0-beta1 released
Posted by Branko Čibej <br...@wandisco.com>.
On 19.03.2015 04:57, Ben Reser wrote:
> I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
> Please choose the mirror closest to you by visiting:
>
> http://subversion.apache.org/download/#pre-releases
>
> The SHA1 checksums are:
>
> cbc62b682e69254f57e40da316ebb7fcf998f56e subversion-1.9.0-beta1.tar.bz2
> 57142f460c51f334429569757974006f275240e8 subversion-1.9.0-beta1.tar.gz
> 66d84c7818d05141e795ed090dba3044c880f6ca subversion-1.9.0-beta1.zip
>
> PGP Signatures are available at:
>
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.bz2.asc
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.tar.gz.asc
> http://www.apache.org/dist/subversion/subversion-1.9.0-beta1.zip.asc
>
> For this release, the following people have provided PGP signatures:
>
> Ben Reser [4096R/16A0DE01] with fingerprint:
> 19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
> Bert Huijben [4096R/CCC8E1DF] with fingerprint:
> 3D1D C66D 6D2E 0B90 3952 8138 C4A6 C625 CCC8 E1DF
> Branko Čibej [4096R/A347943F] with fingerprint:
> BA3C 15B1 337C F0FB 222B D41A 1BCA 6586 A347 943F
> Julian Foad [4096R/4EECC493] with fingerprint:
> 6011 63CF 9D49 9FD7 18CF 582D 1FB0 64B8 4EEC C493
> Philip Martin [2048R/ED1A599C] with fingerprint:
> A844 790F B574 3606 EE95 9207 76D7 88E1 ED1A 599C
> Stefan Fuhrmann [4096R/57921ACC] with fingerprint:
> 056F 8016 D9B8 7B1B DE41 7467 99EC 741B 5792 1ACC
>
> This is a pre-release for what will eventually become Apache Subversion
> 1.9.0. It may contain known issues, a complete list of
> 1.9.0-blocking issues can be found here:
>
>
> http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.9.0
>
> A pre-release means the Subversion developers feel that this release
> is ready for widespread testing by the community. There are known issues
> (and unknown ones!), so please use it at your own risk, though we do
> encourage people to test this release thoroughly. Of particular note, please
> remember than persistent data, such as the working copy or repository
> formats may change before the final release, and there may not be an
> upgrade path from the pre-releases to the final.
>
> As a note to operating system distro packagers: while we wish to have this
> release candidate widely tested, we do not feel that it is ready for packaging
> and providing to end-users through a distro package system. Packaging a
> release candidate poses many problems, the biggest being that our policy lets
> us break compatibility between the release candidate and the final release, if
> we find something serious enough. Having many users depending on a release
> candidate through their distro would cause no end of pain and frustration that
> we do not want to have to deal with. However, if your distro has a branch that
> is clearly labeled as containing experimental and often broken software, and
> explicitly destined to consenting developers and integrators only, then we're
> okay with packaging the release candidate there. Just don't let it near the
> end users please.
>
>
> Release notes for the 1.9.x release series may be found at:
>
> http://subversion.apache.org/docs/release-notes/1.9.html
>
> You can find the list of changes between 1.9.0-beta1 and earlier versions at:
>
> http://svn.apache.org/repos/asf/subversion/tags/1.9.0-beta1/CHANGES
>
> Questions, comments, and bug reports to users@subversion.apache.org.
>
> Thanks,
> - The Subversion Team
Users of Homebrew on Mac OS X can now install this version with
$ brew install subversion --devel
-- Brane
Re: Apache Subversion 1.9.0-beta1 released
Posted by Johan Corveleyn <jc...@gmail.com>.
On Thu, Mar 19, 2015 at 4:57 AM, Ben Reser <br...@apache.org> wrote:
> I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
Is any of the usual binary suppliers (CollabNet, WanDisco, ...)
planning to release a package for Solaris 10 SPARC of this beta?
I'd like to give it a try on a test server machine, but I don't have
the time nor tools to build it from source on Solaris.
I would especially like to try dumping / loading our repository into
the new FSFS format, and see what happens.
--
Johan
RE: Apache Subversion 1.9.0-beta1 released
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Ben Reser [mailto:breser@apache.org]
> Sent: donderdag 19 maart 2015 04:58
> To: Subversion Development; users@subversion.apache.org;
> announce@subversion.apache.org; announce@apache.org
> Subject: Apache Subversion 1.9.0-beta1 released
>
> I'm happy to announce the release of Apache Subversion 1.9.0-beta1.
> Please choose the mirror closest to you by visiting:
>
> http://subversion.apache.org/download/#pre-releases
For whoever is interested in testing this on Windows. The SlikSvn builds of 1.9.0-beta1 are now available as:
https://sliksvn.com/pub/Slik-Subversion-1.9.0-beta1-win32.msi (x86 version)
https://sliksvn.com/pub/Slik-Subversion-1.9.0-beta1-x64.msi (x86_x64 version)
(as usual full debug symbols are available in the https://sliksvn.com/pub/symbols/ directory)
Installing these miss will automatically upgrade your previous version of SlikSvn to this version.
To avoid an installer error on downgrading back to 1.8.x *) manually deinstall this version from the Software control panel, before (re)installing the older version.
Bert
*) The problem is just that setup fails because it can't install with a newer version installed.