You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Table of Contents

Introduction

This document lists the steps necessary to perform a standard release of the Fedora repository software. Each release may include additional steps not included in this outline, particularly as new projects are developed.

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 Admin -> File Releases
    • Select to Add Release on Fedora
    • Enter release name, 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) - 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)
  • 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

Migration Utilities

  • Retrieve a clean checkout of utilities/trunk
  • Build the utilities/trunk using 'ant dist'
  • Copy everything in the utilities/trunk directory into a directory called fedora-{release number}migration and zip that directory into a file called fedora{release number}-migration.zip
  • Use the md5sum tool to create an md5 hash, copy the hash value into a file called fedora-{release number}-migration.md5
  • Upload the zip and md5 files to sourceforge as outlined in the Fedora release section above
  • 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

Journaling RMI Reciever

  • Build self-contained Jar from Fedora trunk with 'ant ??'
  • 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

Cleanup and Backup

  • Create a SVN tag in the tags directory using the released revision of the trunk (copy to ... tags/release-{release number})
  • 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.

Documentation
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels