From: David Lamparter Date: Tue, 4 Jun 2019 16:02:35 +0000 (+0200) Subject: workflow: update notes for release numbering X-Git-Tag: base_7.2~265^2~1 X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=ac97970d241fde8826816ca47b45585b6d2f67be;p=matthieu%2Ffrr.git workflow: update notes for release numbering People have been complaining our major version number increases to fast and/or in a meaningless way... Signed-off-by: David Lamparter --- diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst index 16707c0bdd..6e426afeb5 100644 --- a/doc/developer/workflow.rst +++ b/doc/developer/workflow.rst @@ -73,14 +73,20 @@ Releases FRR employs a ``..`` versioning scheme. ``MAJOR`` - Significant new features or multiple minor features. The addition of a new - routing protocol or daemon would fall under this class. + Significant new features or multiple minor features. This should mostly + cover any kind of disruptive change that is visible or "risky" to operators. + New features or protocols do not necessarily trigger this. (This was changed + for FRR 7.x after feedback from users that the pace of major version number + increments was too high.) ``MINOR`` - Small features, e.g. options for automatic BGP shutdown. + General incremental development releases, excluding "major" changes + mentioned above. Not necessarily fully backwards compatible, as smaller + (but still visible) changes or deprecated feature removals may still happen. + However, there shouldn't be any huge "surprises" between minor releases. ``BUGFIX`` - Fixes for actual bugs and/or security issues. + Fixes for actual bugs and/or security issues. Fully compatible. We will pull a new development branch for the next release every 4 months. The current schedule is Feb/June/October 1. The decision for a ``MAJOR/MINOR``