Versions Compared

Key

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

Table of Contents:

Table of Contents
maxLevel2
outlinetrue
stylenone

...

titleUpdate Needed

...

Introduction

This document lists details the technical steps necessary to perform a standard an official release of Fedora.  It is inteded to be used and updated by the Fedora repository software. Each release may include additional steps not included in this outline, particularly as new projects are developed.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

Steps

Release Release from Fedora trunk

This portion of the release includes the primary Fedora repository software. It is assumed that prior to this point a release branch has been created in SubVersion from trunk and that all testing and last minute changes have been performed against this release branch. It is also assumed that you have a login to SourceForge with administrative access to the Fedora project.

...

  • 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="c05e9849-e415-4733-95d6-2304ec5a424a"><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.

...