-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/11/10 18:41, Pierre-Arnaud Marcelot wrote:
> Hi everyone,
> 
> I'd like to propose that we use Apache's Nexus repository infrastructure to 
> release our future versions on Maven repositories.
> It's used by a large number of Maven based Apache projects now, and it's the 
> recommended way of uploading releases to Maven Repositories, as described on 
> the "Releasing A Maven Project" Guide [1].
> 
> I think we've reach the limit with deployments on people.apache.org... My 
> last deployment of Studio for version 1.5.2 took more than four hours (!!).
> 
> I talked with Chris Custine on that subject and we would probably have a much 
> better performance with Nexus. It also have pretty neat features like 
> stagging that would allow us to upload artifacts and approve (or deny) them 
> later, which could be interesting when voting a release.
> 
> However, there's seem to be one "drawback" in the fact that once the project 
> is moved to Nexus, deployment on people.apache.org are disabled. All 
> deployments must be done on Nexus.
> More information on this on this at INFRA-1896 [2].
> 
> I would really like that we discuss that all together and maybe we could 
> launch a vote to move to Nexus after this discussion.
> 
> WDYT?

I think that's the way to go. Does there also exists a possibility to
deploy at least generated release documentation?

Felix

> 
> Thanks,
> Pierre-Arnaud
> 
> 
> [1] - http://maven.apache.org/developers/release/apache-release.html
> [2] - https://issues.apache.org/jira/browse/INFRA-1896

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuZTOsACgkQ2lZVCB08qHExdACgrH6QmuFnTht0S7y4eaXweQxW
tfkAoKV7bhdyTmuyV6zImFjLXmaCC4e7
=pew2
-----END PGP SIGNATURE-----

Reply via email to