+1 if nexus' team promises to fix as soon as possible any issue encountered in it (to not block apache releases).
cheers Arnaud On Thu, Feb 5, 2009 at 9:50 PM, Jason van Zyl <[email protected]> wrote: > +1 > > > On 5-Feb-09, at 12:31 PM, Brian E. Fox wrote: > > As proposed in separate threads[1][2] and Infra jira[3], we have setup a >> new zone and repository manager for hosting Apache artifacts at >> https://repository.zones.apache.org. The service is now setup and >> several releases of Maven are already staged there. >> >> >> >> The initial idea was to use LDAP for committer auth/authz, but it isn't >> ready yet. In the meantime, a new security realm has been created and >> all Apache committers can log in to the system using their credentials. >> As each project comes over, we will use the existing svn group mappings >> to port the users into the correct group. >> >> >> >> To complete the process of using this for Maven artifacts, the following >> needs to be done: >> >> 1) Configure the new location as a sync source to Central. >> >> 2) Map the rest of the Maven PMC and committer accounts into the >> Maven Group >> >> 3) Move the artifacts from People.apache.org for org/apache/maven/* >> over to the hosted repository >> >> 4) Update documentation on how to release, stage and promote >> >> 5) Adjust the Parent pom to use the new urls for distribution >> management for both snapshots and releases >> >> 6) Release parent poms, update snapshots etc. >> >> >> >> For the time being, we can leave the snapshots in place at p.a.o and >> simply start deploying new versions to the zone. We can setup a proxy of >> the old snapshot and put this into a group with the new one and users >> can migrate over to the new snapshot url and eventually we can move the >> snapshots over. >> >> >> >> We are working with Apache Infra to get a machine neutral dns for this >> [4] and also an official https certificate[5] so hopefully those will >> happen shortly, specifically the dns before we update all the poms. >> >> >> >> The migration of this would happen project by project, with hopefully >> Maven leading the way. >> >> >> >> [1] >> http://www.nabble.com/-Proposal--Use-Nexus-to-actively-manage-the-Apache >> -repository-tt21759239.html#a21759239 >> >> [2] Apache Infra list - I believe there are not public archives of this >> >> [3] https://issues.apache.org/jira/browse/INFRA-1885 >> >> [4] https://issues.apache.org/jira/browse/INFRA-1890 >> >> [5] https://issues.apache.org/jira/browse/INFRA-1891 >> >> >> >> So lets vote: >> >> +1 Yes, lets lead the way at ASF with a better staging and releasing >> process >> >> +0 shrug >> >> -1 No, I like managing my artifacts by hand. >> >> >> >> ---------------------- >> >> Brian Fox >> >> Apache Maven PMC >> >> http://blogs.sonatype.com/brian/ >> >> >> >> > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > We know what we are, but know not what we may be. > > -- Shakespeare > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Arnaud
