Process for releasing xstatic packages
Describes the process to release an xstatic package through standard OpenStack release mechanisms, and also any work required to enable that release process.
All of the below to be documented (https:/
New "gate" development process requires the following to eventually be done:
0. Land U-C support in stable/mitaka (https:/
0. Land stuff in releases repo to allow 4 digit release versions [tonyb]
0. Confirm tagging a release does indeed check PKG_INFO -- the current process does not [tonyb]
Releasing a new xstatic library:
0. Add xstatic_
1. Merge review to xstatic-angular-foo that is the new version: say: 4.0.0.1 [r1chardj0n3s]
2. Follow the steps in http://
New "local" development process [r1chardj0n3s]:
0. Having done a release of an xstatic package...
1. Hand edit local upper-constrati
2. Point $UPPER_
3. When stable, move on to release...
Releasing a new compatible version of Horizon [r1chardj0n3s]:
1. Create a review that bumps U-C for that version - IF NECESSARY - with a workflow block until point 2 is viable so the release team don't accidentally merge
2. Depends-On: The review in 1. for a horizon new-package compatibility change
3. Merge 1 and 2 noting that Horizon (and plugins) will be broken until both have landed
Blueprint information
- Status:
- Complete
- Approver:
- Richard Jones
- Priority:
- High
- Drafter:
- Richard Jones
- Direction:
- Approved
- Assignee:
- Richard Jones
- Definition:
- Approved
- Series goal:
- Accepted for 10.0.0-newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-3
- Started by
- Richard Jones
- Completed by
- Rob Cresswell
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Document additional release process for xstatic
Gerrit topic: https:/
Addressed by: https:/
Update the xstatic release process
