|
|
| (4 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| |
| − | = Feature Freeze =
| |
| | | | |
| − | Feature Freeze is one of the milestones in [[OpenStack]]'s release schedule.
| + | <!-- #REDIRECT [[ReleaseCycle]] --> |
| − | | |
| − | == Before Feature Freeze ==
| |
| − | | |
| − | Before Feature Freeze, anyone is free to implement features, propose them for merging into [[OpenStack]], have it reviewed and, if it gets approved, have it land on trunk.
| |
| − | | |
| − | == After Feature Freeze ==
| |
| − | After Feature Freeze kicks in, we go into bug fixing mode. Only branches that are fixing bugs and do not introduce new features are allowed to enter trunk.
| |
| − | | |
| − | If you have a branch with a feature that you believe has an acceptable importance/risk_of_regression ratio, file a merge proposal and make sure the following conditions are met:
| |
| − | * All your changes must have thorough unit tests. '''Especially''' if your patch touches an area of the code that currently is not well-tested.
| |
| − | * You must provide justification why you think this is important enough to enter the trunk in spite of feature freeze being in effect. This includes a regression potential analysis.
| |
