The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Internal TPs Process for a new software release"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
** Select SyncProtocol (rsync, http, ftp) (currently only RSYNC is supported) | ** Select SyncProtocol (rsync, http, ftp) (currently only RSYNC is supported) | ||
** Upload the Release xml into the ReleaseMetadata field | ** Upload the Release xml into the ReleaseMetadata field | ||
[[Category:WP5-SA2]] | |||
Revision as of 14:59, 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