Difference between revisions of "Internal TPs Process for a new software release"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
=== Pre Requisites === | === Pre Requisites === | ||
* Contact | * Contact the [http://egi.eu/about/staff/Michel_Drescher.html SA2 Activity Manager] to get access to the SW-Release Queue providing a ShortName for your distribution. | ||
* Provide a release.xml (exact filename) according to the [[NRMS_New_Release_MetaDATA_schema]] | * Provide a release.xml (exact filename) according to the [[NRMS_New_Release_MetaDATA_schema]] | ||
=== New Release === | === New Release === |
Revision as of 13:49, 21 October 2010
Pre Requisites
- Contact the SA2 Activity Manager to get access to the SW-Release Queue providing a ShortName for your distribution.
- Provide a release.xml (exact filename) according to the NRMS_New_Release_MetaDATA_schema
New Release
- go to RT and
- Select the Appropriate DistributionShortName (This will be used to create or update the Repository for your release)
- Select the Release Type (Incremental, Non Incremental)
- Choose if it is an Emergency Release or not.
- Type in the SyncURL (i.e where to get the release from)
- Select SyncProtocol (rsync, http, ftp) (currently only RSYNC is supported)
- Upload the Release xml into the ReleaseMetadata field