| Warning | ||
|---|---|---|
| ||
This document needs to be updated to reflect the changes that have occurred since Fedora 3.1. |
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 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 (
...
- )
...
- -
...
- 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
...
- (
...
...
...
...
...
- )
- 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
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
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.
...
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:
...
...
- 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_NUMBERhttp://fedora-commons.org/documentation
...
- /%3Cdiv%20class=
[http://fedora-commons.org/documentation/%3Cdiv%20class=]
- /%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.