It details the technical steps necessary to perform an official release of Fedora.

{toc}

h1. 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.

h1. Release

 Steps


h2. Archive the previous documentation



This step should be done before major changes are made to the documentation wiki for the new release.
* Go to the documentation space's homepage: [http://fedora-commons.org/go/fcr30

]
* Select Browse \-> Advanced

* Select HTML Export

* De-select \_inclusionsLibrary and everything beneath it

* Click Export

* sftp the zip file to the appropriate directory at fedora-commons.org

** Login using the fcrelman account

** Follow the symlink at \~/documentation/

** Create a subdirectory based on the previous version number, e.g., 3.2.1

** Unpack the zip file into the version subdirectory

h2. Tag the

 release

Tag the trunk based on the version of the release (svn copy to tags/release-{version}).



h2. Build the final distribution

TODO: We need a maven target, or targets for this.

The distribution should consist of:
* The fedora-repository installer jar
* The fedora-messaging-client distribution
* The fedora-journaling-rmi-reciever distribution
* An associated .md5 chucksum file for each of the above files

Each filename should include the version number of the Fedora release.




h2. Upload and verify the distribution

Upload all files to the fedora-commons project at sourceforge.net.




h2. Archive the distribution


h1. Old Steps





h2. 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.

* Retrieve a clean checkout of the release branch
* Build the release branch (with JDK 1.5) 'ant release \-Drelease=true'
* Log in to SourceForge and go to the Fedora project
** Go to Project Admin \-> Downloads
** Select to Add Release on Fedora
** Enter release number, create package
** Paste the URL for release notes in 'paste notes' section - then Submit/Release
** Click on URL for 'upload new files' for upload directions.
** Upload all files in the release branch /dist/release directory using web upload ([https://frs.sourceforge.net/webupload|https://frs.sourceforge.net/webupload]) - should be 4 files

** Go back to edit release page and files should be listed under 'Step 2: Add Files' section

** Select all files - select Update

** Set all files to platform independent, select file type. Select Update for each.

** Go to Download \-> Browse All Files and download the files under your new release (that you just put up) to make sure they were uploaded correctly

* Check the MD5 checksum values of each downloaded file ([use the md5sum tool

|http://en.wikipedia.org/wiki/Md5sum])
* Do an install of the Fedora server using the downloaded installer
* Update the file links when clicking on the Download button on SourceForge to point to the newly released files

h2.












h2. Journaling RMI Receiver

* Build zip file containing executable jar and readme doc from Fedora trunk with 'ant rmi-journal-receiver \-Drelease=true'
* Use the md5sum tool to create an md5hash, and put it in a text file called whatever-the-jar-is-named.jar.md5

* Upload the jar and md5 to sourceforce

* In SourceForge, go to Admin \-> File Releases, select to edit the existing project (that you just made) and add the files. Set file types as before.

* Download the files once they are available in the Download \-> Browse All Files section and verify the MD5

 sum

h2.














h2. Cleanup and Backup

* Create a SVN tag in the tags directory using the released revision of the trunk (copy to ... tags/release-\{release number\})
* Create a SVN tag in the the utilities/tags directory using the released version of utilities/trunk
* On fedora server (fedcommsrv1.nsdlib.org) go to /home/fedcommbkup/release-archive/ and create a directory structure using the date and release similar to: 2008/06-13/fedora-3.0b2

* Copy all of the files which were placed on sourceforge into this directory.

h2.

 Documentation

* 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
*** Upload the docs to the website so they show up at /documentation/VERSION_NUMBER[http://fedora-commons.org/documentation/%3Cdiv%20class=]
\[

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

\] |
** 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.

*