Table of Contents:

Introduction

This document This document is intended to be used and kept up to date by the Release Manger.  It details the technical steps necessary to perform an official release of Fedora.  It is inteded to be used and updated by the Release Manager each time we make a new Fedora release.

1. Archive
2. Tag the Release
3. Build the Distribution
4. Upload and Verify the Distribution

Prerequisites

Prerequisites

Before attempting to perform a release, ensure that:

• The test cycle for this release is complete.
• You have an account with commit and release privileges for the fedora-commons project on sourceforge.net. As a committer, you should already have this level of access.
• You have the login details for the fcrelman account at fedora-commons.org.  If you don't have this information yet, you can get it from the previous release manager.

Release Steps

Archive the previous documentation

sdlfkj

Tag the release

adf

Build the distribution

adsf

Upload and verify the distribution

asdf

Archive the distribution

Old Steps

Release from Fedora trunk

...

• Build the Javadocs (ant docs) and add them to the website (see http://fedora-commons.org/documentation/3.1/javadocs)
• Create documentation downloadable "snapshot" in the wiki, of the previous release.
  • You can create a snapshot of the wiki space at any time.  To do it:
    • Go to the space's homepage: http://fedora-commons.org/go/fcr30
    • Select Browse -> Advanced
    • On the left, select HTML Export
    • De-select _inclusionsLibrary and everything beneath it
    • Click Export

    • Wiki Markup
      Upload the docs to the website so they show up at /documentation/VERSION_NUMBER[http://fedora-commons.org/documentation/%3Cdiv%20class=] \[

      <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="34bd35d3e406b348-e5d04b4a-4eea4230-aea5a62e-5078b56ca358636f5c64d3cc"><ac:plain-text-body><![CDATA[

      [http://fedora-commons.org/documentation/%3Cdiv%20class=]]

      ]]></ac:plain-text-body></ac:structured-macro>

  • This should be done prior to any major updates to the current documentation on the wiki
  • The purpose is to always have an archived copy of each prior release's documentation available for viewing on the website.

...