| ... | ... | @@ -14,15 +14,15 @@ The overall versioning strategy proposal and process for OSDU milestone release. |
|
|
|
|
|
|
|
Each release of OSDU libraries and services will have a major/minor version pair (such as "1.0") that represents the release. Release numbers that match across different services are meant to be considered a package -- that is, they were released at the same time. The specific numbers in the version are increased with each release (in the normal way), but importantly are not synchronized to any other milestone name, including monikers such as "R3" or "M1".
|
|
|
|
|
|
|
|
These releases are created as branches with the prefix `release/`, so that the release can be updated with additional patches later. Patches of this nature will not introduce new features, but instead will only apply bugfixes or minor updates.
|
|
|
|
These releases are created as branches with the prefix `release/`, so that the release can be updated with additional patches later. Patches of this nature will not introduce new features but only apply bug fixes or minor updates.
|
|
|
|
|
|
|
|
## Version Tags
|
|
|
|
|
|
|
|
Each release branch will contain tags, one for each patch released under that version. The tags will be named with a `v` prefix and will repeat the version number (such as "v1.0.0"). All release branches will have at least a ".0" patch, but may gain additional tags if patches are applied after branch creation.
|
|
|
|
Each release branch will contain tags, one for each patch released under that version. The tags will be named with a `v` prefix and will repeat the version number (such as "v1.0.0"). All release branches will have at least a ".0" patch but may gain additional tags if patches are applied after branch creation.
|
|
|
|
|
|
|
|
## Tagging Notes
|
|
|
|
|
|
|
|
These pages are generated by scripts to report status on the tagging process.
|
|
|
|
These pages are generated by scripts to report the status of the tagging process.
|
|
|
|
They are mostly relevant to the developers while releases are being prepared.
|
|
|
|
|
|
|
|
* [R2 Gitlab milestone - 0.3](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.3-Tagging-Notes)
|
| ... | ... | @@ -68,14 +68,14 @@ Each OSDU milestone starts with about 1.5 months of development, followed by the |
|
|
|
|
|
|
|
|
|
|
|
Please note that:
|
|
|
|
* `Feature Freeze` is for completion of features development on common code. No new features should be developed for this milestone after this date.
|
|
|
|
* `Feature Freeze` is for the completion of features development on common code. No new features should be developed for this milestone after this date.
|
|
|
|
* Between `Feature Freeze` and `Code Tagging Start`:
|
|
|
|
* No new features should be developed but can still be merged if pending reviews and approvals
|
|
|
|
* Only bug fixes, CSP specific changes, stabilizing pipeline
|
|
|
|
* Only bug fixes, CSP-specific changes, stabilizing pipeline
|
|
|
|
* On the day of `Code Tagging Start`, the release branch is forked from the default (main/master) branch. Release coordinator completes the code tagging.
|
|
|
|
* As soon as code tagging is completed, the tags are deployed to the `QA/Testing Platform Validation` environment.
|
|
|
|
* `Deployed to Pre Shipping` date is the target date for CSP teams to deploy the tagged milestone baseline into pre-shipping env so that preshipping team is able to execute UAT.
|
|
|
|
* Public release date is after the confirmation and validation from pre shipping team. The date may change depending on the validation results.
|
|
|
|
* `Public Release` date is after the confirmation and validation from pre shipping team. The date may change depending on the validation results.
|
|
|
|
|
|
|
|
You may find additional notes about "CSP deployment to QA/Testing (aka "Platform Validation") and Preship environments" in this document.
|
|
|
|
https://gitlab.opengroup.org/osdu/pmc/docs/-/blob/master/Planning/OSDU_Community_Milestone_Release_Process.docx
|
| ... | ... | @@ -87,8 +87,8 @@ _Note that the dates below might change depending on various reasons, announceme |
|
|
|
|Milestones|Feature Freeze| Code Tagging Start |Code Tagging Completed|Deployed to Pre Shipping|Public Release|
|
|
|
|
|----------|--------------|--------------------|----------------------|------------------------|--------------|
|
|
|
|
|M18 |12-May-23 |19-May-23 |26-May-23 |02-Jun-23 |16-Jun-23 |
|
|
|
|
|M19 |23-Jun-23 |30-Jun-23 |7-Jul-23 |14-Jul-23 |28-Jul-23 |
|
|
|
|
|M20 |04-Aug-23 |11-Aug-23 |18-Aug-23 |25-Aug-23 |08-Sep-23 |
|
|
|
|
|M19 |23-Jun-23 |30-Jun-23 |07-Jul-23 |14-Jul-23 |28-Jul-23 |
|
|
|
|
|M20 |04-Aug-23 |11-Aug-23 |18-Aug-23 |25-Aug-23 |08-Sep-23 |
|
|
|
|
|
|
|
|
### Previous dates for OSDU milestone releases (in descending order of dates)
|
|
|
|
|
| ... | ... | |
