| ... | @@ -8,6 +8,8 @@ The overall versioning strategy proposal and process for OSDU milestone release. |
... | @@ -8,6 +8,8 @@ The overall versioning strategy proposal and process for OSDU milestone release. |
|
|
|
|
|
|
|
[**Patch Process**](https://community.opengroup.org/osdu/documentation/-/wikis/Patch-Process)
|
|
[**Patch Process**](https://community.opengroup.org/osdu/documentation/-/wikis/Patch-Process)
|
|
|
|
|
|
|
|
|
[**Dev Environments**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Environments)
|
|
|
|
|
|
|
## Release Branches
|
|
## Release Branches
|
|
|
|
|
|
|
|
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".
|
|
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".
|
| ... | @@ -66,13 +68,14 @@ Each OSDU milestone starts with about 1.5 months of development, followed by the |
... | @@ -66,13 +68,14 @@ Each OSDU milestone starts with about 1.5 months of development, followed by the |
|
|
|
|
|
|
|
|
|
|
|
|
Please note that:
|
|
Please note that:
|
|
|
* Feature freeze is for completion of features development on common code
|
|
* `Feature Freeze` is for 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’:
|
|
* Between `Feature Freeze` and `Code Tagging Start`:
|
|
|
* No new features
|
|
* 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
|
|
|
* Release coordinator (current that is David D.) completes the code tagging
|
|
* On the day of `Code Tagging Start`, the release branch is forked from the default (main/master) branch. Release coordinator completes the code tagging.
|
|
|
* Deployed to pre shipping date is target date for CSP teams to deploy the tagged milestone baseline into pre shipping env so that pre shipping team is ready to execute the tests.
|
|
* As soon as code tagging is completed, the tags are deployed to the `QA/Testing Platform Validation` environment.
|
|
|
* Public release date is after the validation from pre shipping team. The date may change depending on the validation results.
|
|
* `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.
|
|
|
|
|
|
|
|
You may find additional notes about "CSP deployment to QA/Testing (aka "Platform Validation") and Preship environments" in this document.
|
|
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
|
|
https://gitlab.opengroup.org/osdu/pmc/docs/-/blob/master/Planning/OSDU_Community_Milestone_Release_Process.docx
|
| ... | @@ -94,14 +97,14 @@ _Note that the dates below might change depending on various reasons, announceme |
... | @@ -94,14 +97,14 @@ _Note that the dates below might change depending on various reasons, announceme |
|
|
|M17 |17-Mar-23 |31-Mar-23 |13-Apr-23 |19-Apr-23 |10-May-23 |
|
|
|M17 |17-Mar-23 |31-Mar-23 |13-Apr-23 |19-Apr-23 |10-May-23 |
|
|
|
|M16 |27-Jan-23 |03-Feb-23 |17-Feb-23 |22-Feb-23 |15-Mar-23 |
|
|
|M16 |27-Jan-23 |03-Feb-23 |17-Feb-23 |22-Feb-23 |15-Mar-23 |
|
|
|
|M15 |11-Nov-22 |02-Dec-22 |13-Dec-22 |16-Dec-22 |13-Jan-23 |
|
|
|M15 |11-Nov-22 |02-Dec-22 |13-Dec-22 |16-Dec-22 |13-Jan-23 |
|
|
|
|M14 |23-Sep-22 |30-Sep-22 |7-Oct-22 |14-Oct-22 |09-Nov-22 |
|
|
|M14 |23-Sep-22 |30-Sep-22 |07-Oct-22 |14-Oct-22 |09-Nov-22 |
|
|
|
|M13 |22-Jul-22 |4-Aug-22 |12-Aug-22 |19-Aug-22 |09-Sep-22 |
|
|
|M13 |22-Jul-22 |04-Aug-22 |12-Aug-22 |19-Aug-22 |09-Sep-22 |
|
|
|
|M12 |20-May-22 |27-May-22 |24-Jun-22 |28-Jun-22 |12-Jul-22 |
|
|
|M12 |20-May-22 |27-May-22 |24-Jun-22 |28-Jun-22 |12-Jul-22 |
|
|
|
|M11 |18-Mar-22 |28-Mar-22 |1-Apr-22 |15-Apr-22 |03-May-22 |
|
|
|M11 |18-Mar-22 |28-Mar-22 |01-Apr-22 |15-Apr-22 |03-May-22 |
|
|
|
|M10 Patch | |11-Mar-22 |18-Mar-22 |18-Mar-22 |25-Mar-22 |
|
|
|M10 Patch | |11-Mar-22 |18-Mar-22 |18-Mar-22 |25-Mar-22 |
|
|
|
|M10 |14-Jan-22 |21-Jan-22 |28-Jan-22 |11-Feb-22 |4-Mar-22 |
|
|
|M10 |14-Jan-22 |21-Jan-22 |28-Jan-22 |11-Feb-22 |04-Mar-22 |
|
|
|
|M9 |15-Oct-21 |22-Oct-21 |29-Oct-21 |12-Nov-21 |10-Dec-21 |
|
|
|M9 |15-Oct-21 |22-Oct-21 |29-Oct-21 |12-Nov-21 |10-Dec-21 |
|
|
|
|M8 | |27-Aug-21 |3-Sep-21 |17-Sep-21 |30-Sep-21 |
|
|
|M8 | |27-Aug-21 |03-Sep-21 |17-Sep-21 |30-Sep-21 |
|
|
|
|M7 | |16-Jul-21 | |30-Jul-21 |20-Aug-21 |
|
|
|M7 | |16-Jul-21 | |30-Jul-21 |20-Aug-21 |
|
|
|
|M6 | |28-May-21 | | |02-Jul-21 |
|
|
|M6 | |28-May-21 | | |02-Jul-21 |
|
|
|
|M5 | |9-Apr-21 | | |21-May-21 | |
|
|M5 | |09-Apr-21 | | |21-May-21 | |
