This project is read-only.

Proposal of the new Release Process

Jul 12, 2010 at 11:41 AM

Hi All,

 

Below is the proposal of the new Release Process:

 

----
Releasing NPanday
----

Pre-release checklist

* Make sure that the copyright and licenses are on all source code
* Check the build is successful for both NPanday and NPanday-ITs
* Ensure all issues in the tracker for that version have been resolved, or are moved to a later version


Note:

* Generate a sign key and register key at http://pgp.mit.edu/.
* Be sure that the key was already VERIFIED for integrity purposes.
* The following configuration should be added in the settings.xml:

    <profile>
      <id>npanday-release</id>
      <properties>
        <gpg.passphrase>PASSPHRASE_CREATED</gpg.passphrase>
      </properties>
    </profile>


Creating a Release Candidate

Send a proposal in the discussion forum regarding the release and the issues that would be fix in the said release.

The release will be done through the command line.

Steps in releasing NPanday:

1) Check out the code from https://npanday.svn.codeplex.com/svn/npanday-its/trunk/
2) Run 'mvn release:prepare'
3) Fill in the following values:

     * the release version should be <<<1.2.1-RC1>>> or similar (use the release version)
     * the SCM tag should be <<<npanday-1.2.1-RC1>>> or similar (use the release version)
     * check the values for the <Release version> and <Next development version> are correct

4) Check if the tag was successfully created in https://npanday.svn.codeplex.com/svn/releases/<<<SCM tag>>>
5) After successful release:prepare, run 'mvn release:perform -Pnpanday-release -Dtag=url_tag'

Steps in releasing NPanday-ITs

1) Check out the code from https://npanday.svn.codeplex.com/svn/npanday-its/trunk/
2) Run 'mvn release:prepare'
3) Fill in the following values:

     * the release version should ve <<<1.2.1-RC1>>> or similar (use the release version)
     * the SCM tag should be <<<npanday-its-1.2.1-RC1>>> or similar (use the release version)
     * check the values for the <Release version> and <Next development version> are correct

4) Check if the tag was successfully created in https://npanday.svn.codeplex.com/svn/npanday-its/releases/<<<SCM tag>>>
5) After successful release:prepare, run 'mvn release:perform -Pnpanday-release -Dtag=url_tag'


To verify if the release was successful check that the artifacts has been populated in {{http://repo.npanday.org/archiva/repository/npanday-releases/}}


Testing the Release Candidate

Announce the RC and the community will be given a 48 hr window to test.  If the RC passes, same would be done for the final version. eg. <<<1.2.1>>>

Voting on the Release

Post the Majority of Vote on the results of the release.

Finalizing the Release

After the approval of the developers:

* {{{./publishing-docs.html} Publish the site}} for the released version

* Update Download page to upload the msi installer and repository builder from the latest release and mark the version as released.

* Make the announcement in the forum

<<Note:>> If a serious flaw is found in the release, the release version will not be removed in the distribution list
            but instead a new release (1.2.2) should be provided.

Jul 15, 2010 at 6:19 AM
reviewed what you checked in, it looks good to me