- Create release maintenance and engineering branches in head (usually off master upon feature freeze). Push to sf.net.
- example names: "g-maint", "g-release"
- Create release maintenance and engineering branches in plugins (usually off master upon feature freeze). Push to sf.net.
- Bump version numbers for maven modules on the master branch to differentiate artifact versions from those in the imminent release (for an example, see MIFOS-3861). Never bump revisions on release maintenance branches.
- Maintain current.release.name Maven build property on release maintenance branch. (example right after creating branch, near-release example)
- Maintain current.release.name Maven build property on master. (example)
- Change plugin dependency version numbers on plugins/master to those on head/master.
- Create ci jobs for the new release maintenance branches. Delete the ci job for the branch before the previous one (for instance, if you create head-g-release, delete the head-e-release job).
- Create a test server for the new release maintenance branch on head/master.
- Update Test Servers.
Manage space
Manage content
Integrations