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
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
2012/2/13 Daniel Shahaf :
> [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
>> wrote:
>> > Currently we publish releases by uploading them to a specified directory
>> > on scp://people.apache.org/.
>> >
>> > Infra wo
[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
> 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
On Mon, Feb 13, 2012 at 9:02 AM, Daniel Shahaf 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 j
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 u
6 matches
Mail list logo
