On Fri, Mar 23, 2012 at 3:54 PM, Stefan Sperling <stsp_at_apache.org> wrote:
> Subversion-1.6.18 tarballs are now available for testing/signing by
> committers. To obtain them please check out a working copy from
> https://dist.apache.org/repos/dist/dev/subversion
>
> Please add your signatures to the .asc files there.
> You can use the release.py script for this:
> release.py sign-candidates --target /path/to/dist/dev/subversion/wc 1.6.18
> which is the equivalent of running the following command for each tarball:
> gpg -ba -f - subversion-1.6.18.tar.bz2 >> subversion-1.6.18.tar.bz2.asc
>
> Since this is a 1.6.x release there are -dep tarballs
> which should also be signed by those who test them.
> I've run a test build with these dependencies on a Debian Linux system.
>
> While signatures for this release are collected via dist.apache.org
> the release won't be made from apache.org but from tigris.org.
>
> Downstream packagers, please keep in mind that this release is not
> blessed yet. Please do not distribute binaries compiled from these
> sources before the release has been officially announced. This release
> may still be pulled and supplanted by a different one (with a new version
> number) in case of unforeseen problems during the testing phase.
Concerning the Windows sigs: I'm afraid I can't help ATM.
Though my interest in another 1.6 release is quite low from a personal
standpoint (and @work we're about to migrate everyone to 1.7), I
wouldn't mind letting my laptop do some useful work to be able to
provide a sig. It's just that ... it's been a hell of a busy week both
@home and @work for me, so I haven't gotten around to it. So I hope
some of the other Windows devs can do it. If not, I'll try to make
some time during the weekend, and send my signature by Monday morning.
--
Johan
Received on 2012-03-30 11:41:11 CEST