Versions Compared

Old Version 19

changes.mady.by.user Richard McGuire

Saved on

compared with

New Version 20

changes.mady.by.user Jarek Gawor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Copy from the staging repo to the production repo.
    Once the release is deemed fit for public consumption it can be transfered to a production repository where it will be available to all users. Note: Current version of the stage plugin is 1.0-alpha-1.
    Here is an example on how to use the stage plugin:
    No Format
    mvn stage:copy -Dsource="http://people.apache.org/<your apache id>/staging-repo/<siteId>" \
  -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \
  -Dversion=2.1.2 \
  -DtargetRepositoryId=apache.releases
    Note

    The version parameter is currently ignored but specify the correct version anyway. The entire staging repository is synced, not just the given version or the current project.

    Note

    Also note, this process has been known to have problems at times if a maven version other than 2.0.8 is used.

  2. Copy the distribution content from the staging location to the production repo.
    From your people apache account copy Check in the distribution content to into the appropriate location under in https:/www/wwwEnsure that the files you copy to the rsync and distribution directories have 0775 dir permission and a 0664 file permission set on themdist.apache.org/repos/dist/release/geronimo/ InfoImage Added.
  3. Move the branches to tags using the following command.
    No Format
    svn mv SRC-URL DEST-URL -m "Reason for this commit".
  4. Update the Geronimo site download pages with a new page for the release Geronimo Downloads . Include the list JIRA for know issues by first generating a JIRA query for the release, right clicking on the XML format and saving the url to inclusion in the download page.
  5. Administer the GERONIMO JIRA project to update the released and unreleased versions
  6. Update the Geronimo Home Page with a News item that a new Geronimo Server release is available
  7. Update the Geronimo Release Roadmaps with the release date.
  8. Final step, is to force the Confluence Autoexport plugin to run for the following spaces: Apache Geronimo (GMOxSITE), Apache Geronimo Project Management (GMOxPMGT), Apache Geronimo 2.1 (GMOxDOC21)

...