FRR: Update Community.md to reflect release process #1784
Conversation
This is the new release process for FRR. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-2629/ This is a comment from an EXPERIMENTAL automated CI system. CLANG Static Analyzer Summary
19 Static Analyzer issues remaining.See details at |
There was a problem hiding this comment.
This looks fine to me, but I think @louberger and maybe some others need to approve as well before merging.
| A example of a MINOR feature is the addition of the BGP Shutdown feature. | ||
| * BUGFIX - Fixes for actual bugs and/or security issues. | ||
|
|
||
| We will pull a new development branch for the next release every 4 months. |
There was a problem hiding this comment.
Isn't master the 'development' branch? Perhaps a different name would be less confusing.
| will be updated to reflect the next possible release name to allow | ||
| for easy distinguishing. Additionally the new dev branch will have | ||
| these files updated too. | ||
|
|
There was a problem hiding this comment.
The expectation / process covering what happens during the 1st month should be defined / captured. (Is it more than changing configure.ac and packaging? if not, why a month, if yes, what...)
|
|
||
| Security issues are fixed for 1 year minimum on old releases and | ||
| normal bug fixes for the current and previous release | ||
|
|
There was a problem hiding this comment.
what happens on release? perhaps the branch renamed/created called rel/MAJOR.MINOR?
FRR: Update Community.md to reflect release process
|
Although late, quick question... Is API and ABI compatibility maintained only within the same MAJOR.MINOR or MAJOR (semver like)? I think API and ABI compatibility should be part of the guide. |
|
@msune We presently do not have any version controls on API or ABI compatibility. I agree with you that this should be part of our versioning scheme. |
This is the new release process for FRR.
Signed-off-by: Donald Sharp sharpd@cumulusnetworks.com