directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <fel...@apache.org>
Subject Re: Release process for internal projects
Date Sun, 26 Sep 2010 19:01:35 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/26/10 13:13, Stefan Seelmann wrote:
> Hi devs,
> 
> I'd like to release a new version of the Skins project and have
> questions regarding the relaese process.
> 
> My understanding for releasing a project (Shared, ApacheDS, Studio) is
> the following:
> 0. Consensus to cut a new release
> 1. Run mvn release:prepare (which creates a tag in svn) and mvn
> release:perform (which deploys maven artifacts to a staging repository
> on Nexus and deploys the site to p.a.o). Additional binaries are
> deployed to p.a.o for testing.
> 2. Launch a 72 hr vote
> 3. If the vote passes the staging repository is released, otherwise
> the staging repostiory is dropped and + goto 0

Does there exists any docu how it works (releasing to stagin repository
and 'going live' from staging or dropping from staging after 72 hours?

> Please correct me if I'm wrong.
> 
> My question is if we use the same process for our internal projects
> (Skins, JUnit Add-ons, Checkstyle)?
> 
> We also have a simplified process for releasing a new TLP pom [2].
> Maybe it's an option to use this process for the internal projects?
> 
> Thoughts?

+1
Regards
Felix

> [1] https://cwiki.apache.org/confluence/display/DIRxDEV/Guide+to+Directory+Releases
> [2] https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy
> 

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

iEYEARECAAYFAkyfmI8ACgkQ2lZVCB08qHGwPgCeK3vHxtgZ1QD8Sei3CK1fXpqj
vEgAnizVFgCutXXju2uJjgeU2DfOGw1g
=a9NW
-----END PGP SIGNATURE-----

Mime
View raw message