Skip to content

Changes

Page history
Update Release Strategy authored by Chad Leong's avatar Chad Leong
Hide whitespace changes
Inline Side-by-side
Release-Strategy.md
View page @ 9a4d6dce
......@@ -14,7 +14,7 @@ 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 only apply bug fixes 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
......@@ -63,9 +63,9 @@ They are mostly relevant to the developers while releases are being prepared.
## Development timeline for milestones
Each OSDU milestone starts with about 1.5 months of development, followed by the check points of: feature freeze, code freeze, code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
Each OSDU milestone starts with about 1.5 months of development, followed by the checkpoints of: feature freeze, code freeze, code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
![Release Process](uploads/ad6e073a3e3c980ebd19be11579a0989/image.png)
![Release Process](uploads/270c1ded2bc1c0a853ef7252274a7f44/image.png)
Please note that:
* `Feature Freeze` is for the completion of features development on common code. No new features should be developed for this milestone after this date.
......@@ -86,9 +86,9 @@ _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 |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 |
|M18 |12-May-23 |19-May-23 |~~26-May-23~~ 02-Jun-23|02-Jun-23 |~~16-Jun-23~~ 23-Jun-23 |
|M19 |30-Jun-23 |07-Jul-23 |14-Jul-23 |21-Jul-23 |11-Aug-23 |
|M20 |18-Aug-23 |25-Aug-23 |01-Sep-23 |08-Sep-23 |29-Sep-23 |
### Previous dates for OSDU milestone releases (in descending order of dates)
......