| ... | ... | @@ -56,19 +56,3 @@ Below is the current planned date for upcoming OSDU milestone releases. |
|
|
|
|M10 |7-Jan-22 |14-Jan-22 |21-Jan-22 |28-Jan-22 |11-Feb-22 |
|
|
|
|
|
|
|
|
* M10 cycle is longer with consideration of Christmas and new year holiday |
|
|
|
|
|
|
|
# Creation Process
|
|
|
|
|
|
|
|
## Creating a new Release
|
|
|
|
|
|
|
|
_Because the_ `release/*` and `v*` wildcards are protected, only maintainers can perform these tasks.
|
|
|
|
|
|
|
|
Before starting to release projects, create a release branch and initial tag for the [CI-CD Pipelines project](https://community.opengroup.org/osdu/platform/ci-cd-pipelines). This will create a stable pipeline reference, which is used later in other services.
|
|
|
|
|
|
|
|
Then, for each service, create a branch based on the default branch, and name it appropriately ("release/X.Y"). As the first commit to that branch, update the `.gitlab-ci.yml` file to reference the corresponding release tag of the CI-CD Pipelines projects. Once pushed, a full protected pipeline should execute on the release branch. _(If this does not happen, check your repository settings to ensure that_ `release/*` is a protected branch, and `v*` is a protected tag).
|
|
|
|
|
|
|
|
After the release pipeline passes and/or you are satisfied with the results, create a tag for the first patch ("vX.Y.0"). Once created, the tag will run a full protected pipeline as well.
|
|
|
|
|
|
|
|
## Creating a new Patch
|
|
|
|
|
|
|
|
If a new patch is needed on a particular service, simply add the new commits to the release branch, either with cherry picks or merges. Then, wait for the new pipeline to succeed, and create a new tag on the branch incrementing the patch number (for example, "vX.Y.1"). If new CI-CD Pipelines are needed for the patch, don't forget to update the `.gitlab-ci.yml` file to reference the new version of the CI-CD includes. |
|
|
\ No newline at end of file |
