... | @@ -30,8 +30,18 @@ Update Policy |
... | @@ -30,8 +30,18 @@ Update Policy |
|
|
|
|
|
Each platform stream has different update policy since they targets different use cases.
|
|
Each platform stream has different update policy since they targets different use cases.
|
|
|
|
|
|
* ELT Platform Next
|
|
* **ELT Platform Next**
|
|
* No restrictions on braking changes
|
|
* No restrictions on braking changes
|
|
|
|
* Ideally teams coordinate updates to avoid packages breaks
|
|
|
|
* **Yearly Branches**
|
|
|
|
* Projects may introduce breaking changes only till the release date scheduled in XXX.
|
|
|
|
* Breaking changes that are unanimously agreed between all affected projects are allowed.
|
|
|
|
* Updates containing bug-fixes and new features are allowed and can be merged any time.
|
|
|
|
* All updates has to pass staging pipelines before provided to users.
|
|
|
|
* Each broken test has to be examined individually. I.e. flaky test or improper API usage doesn't block the update.
|
|
|
|
* **Release Branches**
|
|
|
|
* Any update has to be unanimously agreed by owners of the release branch
|
|
|
|
* All updates has to pass staging pipelines before provided to users.
|
|
|
|
|
|
## Versioning
|
|
## Versioning
|
|
|
|
|
... | | ... | |