Difference between revisions of "EGI-InSPIRE:NSRW New Software Release Workflow"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
# The SW Provider creates a Ticket in GGUS accompanied with all the necessary info: | # The SW Provider creates a Ticket in GGUS accompanied with all the necessary info: | ||
## Release notes, or the link to them. The release notes should link to the advisory written by the Software Vulnerability Group (SVG), | ## Release notes, or the link to them. The release notes should link to the advisory written by the Software Vulnerability Group (SVG), in the case of a software vulnerability. | ||
in the case of a software vulnerability. | |||
## Changelog, or the link to it. This can be already provided either inside the package or be part of the release notes. | ## Changelog, or the link to it. This can be already provided either inside the package or be part of the release notes. | ||
## Certification report(s) (from the agreed quality assurance documentation and tests) or a link. | ## Certification report(s) (from the agreed quality assurance documentation and tests) or a link. | ||
## Link to documentation: users manual, system administration manual, etc. The documentation should be updated if applicable, | ## Link to documentation: users manual, system administration manual, etc. The documentation should be updated if applicable, for example if the release introduces new functionality. | ||
for example if the release introduces new functionality. | |||
## Links to all bugs, issues, features in this new release. This can be already provided either inside the package or be part of the release notes. | ## Links to all bugs, issues, features in this new release. This can be already provided either inside the package or be part of the release notes. | ||
# The ticket is transferred from GGUS to RT, the RepoAction field of the ticket is “MoveToUnverified“ | # The ticket is transferred from GGUS to RT, the RepoAction field of the ticket is “MoveToUnverified“ |
Revision as of 17:08, 22 September 2010
Ticket LifeCycle
- The SW Provider creates a Ticket in GGUS accompanied with all the necessary info:
- Release notes, or the link to them. The release notes should link to the advisory written by the Software Vulnerability Group (SVG), in the case of a software vulnerability.
- Changelog, or the link to it. This can be already provided either inside the package or be part of the release notes.
- Certification report(s) (from the agreed quality assurance documentation and tests) or a link.
- Link to documentation: users manual, system administration manual, etc. The documentation should be updated if applicable, for example if the release introduces new functionality.
- Links to all bugs, issues, features in this new release. This can be already provided either inside the package or be part of the release notes.
- The ticket is transferred from GGUS to RT, the RepoAction field of the ticket is “MoveToUnverified“
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Downloads the software bundle and puts it on the “Unverified” Repository
- The Repo parses the attached xml
- Based on the metadata contained at both, the ticket itself and the attached xml, the Repo performs the necessary actions
- Upon success: The Repo updates the RT setting the RepoStatus of the ticket to “Unverified” + the Uri where the new software can be found, etc.
- In case of a failure: The Repo updates the RT, setting the RepoStatus of the ticket to “Failed”, plus it updates the ticket with a comment that contains the info related to the failure
- In both 4.c cases, the RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG)
- EGI TUG -- please fill in the intermediate steps here concerning the 4.3.1 step.
- EGI TUG -- please fill in the intermediate steps here concerning the 4.3.2 step.
- If the TUG team decide that the release it is ready to move to stage-rollout phase, the RepoAction field of the ticket it is marked as MoveToStageRollOut
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Move the SW to stage-rollout
- The Repo updates the RT setting the RepoStatus of the ticket to “Stage-Rollout” + the Uri where the new software can be found, etc.
- RT Notifies the EA and/or MarioD or whoever is responsible to handle the stage-rollout process (MarioD?? any suggestion on this?)
- If everything it is OK, MarioD change the RepoAction field to “MoveToProduction”
- Upon RepoAction field change, the RT Notifies the Repo that there is a ticket to be processed
- The Repo Processes the ticket
- Move the SW to production
- The Repo updates the RT setting the RepoStatus of the ticket to “Production” + the Uri where the new software can be found, etc.
…. and the life goes on ….
...
Required Fields
RepoAction : Actions to Be Performed by the Repo, Values MoveToUnverified,MoveToStageRollOut,MoveToProduction,Reject,Depreceate
RepoStatus : Response to RepoActions, Values Uverified,StateRollOut,Production,Depreceated,Failed
Work Flow
MetaData
NRMS New Release MetaDATA schema
Ticket Status Values
Questions/Issues
Insert any question / issue you may have here to keep track of them