mirror/bind9
1
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9.git synced 2025-12-20 00:55:29 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
Page: BIND 9.11 ESV Soft Code Freeze
Pages
"main" branch partial history rewrite in August 2022 A few thoughts on Rust in BIND BIND 9 Achievements BIND 9 F2F Meeting in Warsaw, October 2019 BIND 9 Memory Explained BIND 9 PKCS11 BIND 9 Packaging BIND 9 Style Guide BIND 9.11 ESV Soft Code Freeze BIND 9.15 Plan BIND 9.17 Plan BIND 9.19 Plan BIND 9.19 Planning: CHANGES BIND 9.19 Planning: Configuration Backend BIND 9.19 Planning: DB notes BIND 9.19 Planning: Discuss new features BIND 9.19 Planning: Incident Manager Rotation BIND 9.19 Planning: Netmgr evaluation BIND 9.19 Planning: Refactor RBTDB BIND 9.19 Planning: Refactoring XFR BIND 9.19 Planning: Refactoring zone.c BIND 9.19 Planning: Refactoring BIND 9.19 Planning: Statistics System Overhaul BIND 9.19 Planning: Testing BIND 9.19 Planning: Things to do before BIND 9.18 cutoff BIND 9.21 Plan BIND Development and Release Process 2019 BIND development workflow BIND9 Databases CGroups v2 limiting resource consumption for testing CPU profiling using perf Config system requirements DNS Shotgun integration into Gitlab CI DNSSEC Key and Signing Policy (KASP) Data structure survey Debian Packages Escalation Engineer Duties Git Of Theseus Gitlab how to How to setup Docker image with core file Integration tests wish list Internal objects and their relations Known Issues in BIND 9.18 Known Issues in BIND 9.20 Known Issues in BIND 9.21 LLM based tools thoughts Planning Policy for removing named.conf options Preparing Useful Merge Requests QP‑trie in NSD Requirements and Designs Server side Git hooks Serving stale data Stable Release Update Statistics Requirements SystemTap on 4326 remove locking from copy_namehook_lists SystemTap on main Team Meetings Testing by configuration options Updating resolver algorithm, or "who knows best, the parent or the child?" User space Probing in BIND 9 _sidebar benchmarks best practices caches dashboard home october2018meeting pytest howto stdatomic usage in master
Clone
2
BIND 9.11 ESV Soft Code Freeze
Ondřej Surý edited this page 2020-04-09 09:40:17 +00:00

BIND 9.11 Release branch has been put on Soft Code Freeze as of .

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. P.P.S.: This applies only for BIND 9.11 ESV Open Source edition, it does not apply to BIND 9.11 ESV Subscription Edition.