| ... | ... | @@ -31,16 +31,21 @@ Each release branch will contain tags, one for each patch released under that ve |
|
|
|
|
|
|
|
## Development timeline for milestones
|
|
|
|
|
|
|
|
Each OSDU milestone starts with about 1.5 months of development, followed by the 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 check points of: feature freeze, code freeze, code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Below is the current planned date for upcoming OSDU milestone releases. Note that:
|
|
|
|
|
|
|
|
* Code freeze date is for development teams to complete the new function development and integration in this release.
|
|
|
|
Please note that:
|
|
|
|
* Feature freeze is for completion of features development on common code
|
|
|
|
* Between ‘Feature Freeze’ and ‘Code Freeze’:
|
|
|
|
* No new features, No common code change
|
|
|
|
* Only bug fixes, CSP specific changes, stabilizing pipeline
|
|
|
|
* Release coordinator (current that is David D.) 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.
|
|
|
|
* Public release date is after the validation from pre shipping team. The date may change depending on the validation results.
|
|
|
|
|
|
|
|
Below is the current planned date for upcoming OSDU milestone releases.
|
|
|
|
|
|
|
|
| Milestones | Code freeze date for Dev teams | Deployed to Pre Shipping | Public release date |
|
|
|
|
|------------|--------------------------------|--------------------------|---------------------|
|
|
|
|
| M5 | Apr 9, 2021 | | May 2021 |
|
| ... | ... | |
