You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Shahaf <d....@daniel.shahaf.name> on 2012/02/13 16:02:16 UTC
Moving our dist area to svnpubsub
Currently we publish releases by uploading them to a specified directory
on scp://people.apache.org/.
Infra would like to move from this model to a model where releases are
stored in a Subversion repository[1].
I suggest that we join a few other PMC's who had already converted. The
impact on us is that we'll be uploading releases by committing to
[1]/subversion, rather than by scp'ing them. It will also shorten the
wait period on mirroring new releases from 25 hours to 24 hours.
Barring objections I'll follow up with infra in a few days to make this
happen.
Daniel
[1] https://dist.apache.org/repos/dist/release/
Re: automatically verifying PGP sigs on dist.a.o Re: Moving our dist
area to svnpubsub
Posted by Konstantin Kolinko <kn...@gmail.com>.
2012/2/13 Daniel Shahaf <d....@daniel.shahaf.name>:
> [CC += infra]
>
> Hyrum K Wright wrote on Mon, Feb 13, 2012 at 09:08:26 -0600:
>> On Mon, Feb 13, 2012 at 9:02 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>> > Currently we publish releases by uploading them to a specified directory
>> > on scp://people.apache.org/.
>> >
>> > Infra would like to move from this model to a model where releases are
>> > stored in a Subversion repository[1].
>> >
>> > I suggest that we join a few other PMC's who had already converted. The
>> > impact on us is that we'll be uploading releases by committing to
>> > [1]/subversion, rather than by scp'ing them. It will also shorten the
>> > wait period on mirroring new releases from 25 hours to 24 hours.
>> >
>> > Barring objections I'll follow up with infra in a few days to make this
>> > happen.
>>
>> That would be awesome. Despite my past obstinacy, I'm particularly
>> attracted to the part where PMC members would be able to directly
>> commit their signatures to the release area, where something (an
>> svnpubsub instance?) then verifies the sigs.
>>
>
> +1.
>
> As to the implementation: we could run something off of svnpubsub to
> verify the signatures, but I wonder if it'd make more sense to do that
> ASF-wide in the pre-commit hook on dist.apache.org. Infra people ---
> thoughts?
>
Afaik there is already a cron job that does verification,
http://people.apache.org/~henkp/
-> pgp checks
-> sig/md5 checker documentation
Do you think that the hook should verify that the key is "trusted" and
reject the commit, or just nag? I, personally, would prefer nagging as
there might be different issues, and PMC may need some time to resolve
the issue.
Best regards,
Konstantin Kolinko
automatically verifying PGP sigs on dist.a.o Re: Moving our dist
area to svnpubsub
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
[CC += infra]
Hyrum K Wright wrote on Mon, Feb 13, 2012 at 09:08:26 -0600:
> On Mon, Feb 13, 2012 at 9:02 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> > Currently we publish releases by uploading them to a specified directory
> > on scp://people.apache.org/.
> >
> > Infra would like to move from this model to a model where releases are
> > stored in a Subversion repository[1].
> >
> > I suggest that we join a few other PMC's who had already converted. The
> > impact on us is that we'll be uploading releases by committing to
> > [1]/subversion, rather than by scp'ing them. It will also shorten the
> > wait period on mirroring new releases from 25 hours to 24 hours.
> >
> > Barring objections I'll follow up with infra in a few days to make this
> > happen.
>
> That would be awesome. Despite my past obstinacy, I'm particularly
> attracted to the part where PMC members would be able to directly
> commit their signatures to the release area, where something (an
> svnpubsub instance?) then verifies the sigs.
>
+1.
As to the implementation: we could run something off of svnpubsub to
verify the signatures, but I wonder if it'd make more sense to do that
ASF-wide in the pre-commit hook on dist.apache.org. Infra people ---
thoughts?
> In addition to working with Infra, release.py would probably need to be updated.
>
> -Hyrum
>
>
> --
>
> uberSVN: Apache Subversion Made Easy
> http://www.uberSVN.com/
Re: Moving our dist area to svnpubsub
Posted by Hyrum K Wright <hy...@wandisco.com>.
On Mon, Feb 13, 2012 at 9:02 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Currently we publish releases by uploading them to a specified directory
> on scp://people.apache.org/.
>
> Infra would like to move from this model to a model where releases are
> stored in a Subversion repository[1].
>
> I suggest that we join a few other PMC's who had already converted. The
> impact on us is that we'll be uploading releases by committing to
> [1]/subversion, rather than by scp'ing them. It will also shorten the
> wait period on mirroring new releases from 25 hours to 24 hours.
>
> Barring objections I'll follow up with infra in a few days to make this
> happen.
That would be awesome. Despite my past obstinacy, I'm particularly
attracted to the part where PMC members would be able to directly
commit their signatures to the release area, where something (an
svnpubsub instance?) then verifies the sigs.
In addition to working with Infra, release.py would probably need to be updated.
-Hyrum
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/
Re: Moving our dist area to svnpubsub
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
This is now in place.
We have https://dist.apache.org/repos/dist/dev/subversion/
and https://dist.apache.org/repos/dist/release/subversion/ ,
with the latter is tied via svnpubsub to the master distribution
site (and the rsync seed for mirrors).
I imagine we'll use the /release tree just like we used the rsync seed
location so far --- that is, only upload tarballs to it that are signed
and blessed.
How do we want to use the /dev tree?
(Some options include: use it for unblessed tarballs undergoing
signature collection; use it for blessed pre-release tarballs; don't use
it. (non-exhaustive list))
Re: Moving our dist area to svnpubsub
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
No objections so I'll go ahead and ask infra to implement this.
The one variable here is "what mailing list to send commit mails to".
I'm assuming dev@. (commits@ is the other option)
Daniel Shahaf wrote on Mon, Feb 13, 2012 at 17:02:16 +0200:
> Currently we publish releases by uploading them to a specified directory
> on scp://people.apache.org/.
>
> Infra would like to move from this model to a model where releases are
> stored in a Subversion repository[1].
>
> I suggest that we join a few other PMC's who had already converted. The
> impact on us is that we'll be uploading releases by committing to
> [1]/subversion, rather than by scp'ing them. It will also shorten the
> wait period on mirroring new releases from 25 hours to 24 hours.
>
> Barring objections I'll follow up with infra in a few days to make this
> happen.
>
> Daniel
>
>
>
>
>
> [1] https://dist.apache.org/repos/dist/release/