Versions Compared

Key

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

...

The previous release version (snapshot previous documentation) is identifed identified as A.B, replace this with the previous release (eg 3.6).

...

  • You have an account with commit, release, and shell access for the fedora-commons project on sourceforge.net. As a committer, you should already have this level of access.
  • You have an account with manager privileges on the Fedora Commons Plone wiki.
  • You have an account with edit privileges on the duraspace.org Confluence wiki.
  • You have an oss.sonatype.com account and have requested to be given permission to publish to the org.fcrepo groupId by adding a comment to the Fedora Sonatype Hosting Ticket
  • Your maven settings.xml includes the following:

...

If any online resources have been modified or added to during the release, these must be updated. Particularly XSD schema files served at http://www.fedora-commons.org/definitions/1/0/ must be verified.

Release Day

Update documentation area on the Fedora Commons wiki

Fedora Commons Wiki (Plone): http://www.fedora-commons.org/Image Added
Sitemap: http://www.fedora-commons.org/sitemapImage Added

  1. Copy Software -> Current Release to Software -> Previous Releases -> Release X.Y
    Move Release X.Y to the top of the list of release pages.
    Change state to published in green view tab, state: in green right-hand drop-down menu
    Select Release X.Y as the default page to display for the Previous Releases folder:
    • navigate to Previous Releases folder
    • select green view tab
    • select display drop-down menu
    • select change content item as default view...
  2. Edit Software -> Current Release to refer to the new version of the software
  3. Edit the Software page to update the Download link: http://downloads.sourceforge.net/fedora-commons/fcrepo-installer-X.Y.Z.jarImage Added
  4. Edit the Home page:
  5. Edit the Announcements folder:
    • add a Fedora Repository X.Y.Z Released page
    • move the page to top of Announcements list
    • On the day of the announcement:
      • change state the state of the page to published
      • expire previous release announcement page

Update the KEYS file

Make sure the KEYS file in subversion is up-to-date with the latest, exported public keys of the committers (and most importantly, the release manager).  For more information on this file, see this page.

...