Release 3 Change Control Process
The goal of the change control process is to minimize the risk of destabilizing the R3 code while the project prepares for it's General Availability release.
- Any proposed patch must have an associated Ticket.
- Maintainers should use the existing, standard process to create, review, and test patches.
- Once a maintainer is ready to submit a patch to the staging branch, they should request a review from the Release Manager (Steve Constant steve.constant at hp.com).
- The Release Manager will ensure that the patch has an associated ticket, and that the priority of the ticket is Blocker or Critical, and then give approval to the maintainer to submit the patch.
- Please only submit changes to the R3 branch that have gone though the above process. I will not be locking the branch, so following the above process is important.
Questions/comments should be directed to Steve Constant (steve.constant at hp.com)
