|
|
BIND 9.11 Release branch has been put on Soft Code Freeze as of <date>.
|
|
|
|
|
|
That means there will be restrictions on the amount of the code we regularly backport to v9_11 branch.
|
|
|
|
|
|
The only class of things that we will semi-automatically backport to BIND 9.11 are:
|
|
|
|
|
|
- high and critical security fixes
|
|
|
- critical bug fixes
|
|
|
- FTBFS fixes
|
|
|
|
|
|
All these changes will have to be at least discussed with Support Team (e.g. we will
|
|
|
put the list into the pad) and signed-off by either Security Officer, or Support team
|
|
|
member, or Director of DNS Engineering (@ondrej) or BIND 9 QA Manager (@michal).
|
|
|
|
|
|
Any other changes will have to be discussed during with the Support Team
|
|
|
and signed-off by either Security Officer or Support team member _AND either Director
|
|
|
of DNS Engineering (@ondrej) or Head of BIND 9 QA (@michal).
|
|
|
|
|
|
The double sign-off needs includes (not a complete list):
|
|
|
|
|
|
- medium security fixes
|
|
|
- protocol maintenance
|
|
|
|
|
|
Exempts to this rule:
|
|
|
|
|
|
- unit and system tests enhancements and fixes (more tests are always good)
|
|
|
|
|
|
Things that should not be backported ever:
|
|
|
|
|
|
- cosmetic fixes
|
|
|
- feature enhancements
|
|
|
|
|
|
P.S.: For the next ESV, I will try to impose the Soft Code Freeze way earlier. |