[dev] Reply: FRR 7.1 & 8.0 release timelines

[Hansen, Christoffer]

On 20/05/2019 07:02, Narendra Bandarupalli wrote:
> Can someone please share planned release dates for FRR 7.1 and 8.0
> releases.
> 
> I see FRR 7.1 milestone is created – all submits into master branch as on
> today are targeted for 7.1 release?

http://docs.frrouting.org/projects/dev-guide/en/latest/workflow.html?highlight=releases#releases

See information available in the documentation.

If the information is unclear in any way. Could you be more specific in
your question?

> FRR employs a <MAJOR>.<MINOR>.<BUGFIX> versioning scheme.
> 
> MAJOR
>     Significant new features or multiple minor features. The addition of a new routing protocol or daemon would fall under this class.
> MINOR
>     Small features, e.g. options for automatic BGP shutdown.
> BUGFIX
>     Fixes for actual bugs and/or security issues.
> 
> 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 release is made at the time of branch pull based on what has been received the previous 4 months. The branch name will be dev/MAJOR.MINOR. At this point in time the master branch and this new branch, configure.ac, documentation and packaging systems will be updated to reflect the next possible release name to allow for easy distinguishing.
> 
> After one month the development branch will be renamed to stable/MAJOR.MINOR. The branch is a stable branch. This process is not held up unless a crash or security issue has been found and needs to be addressed. Issues being fixed will not cause a delay.
> 
> Bugfix releases are made as needed at 1 month intervals until the next MAJOR.MINOR release branch is pulled. Depending on the severity of the bugs, bugfix releases may occur sooner.
> 
> Bugfixes are applied to the two most recent releases. However, backporting of bug fixes to older than the two most recent releases will not be prevented, if acked under the classical development workflow applying for a pull request.
> 
> Security fixes are backported to all releases less than or equal to at least one year old. Security fixes may also be backported to older releases depending on severity.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20190520/5835778e/attachment.sig>