There has been a non-trivial number of bug-fixes and improvements of FRR in the intervening year. https://github.com/FRRouting/frr/blob/master/doc/developer/workflow.rst Look at paragraph starting at line 102 for our policy. We are approaching a point where 3.0 is no longer going to be supported in general( not that there has been a bunch of support for it yet either ). donald On Thu, Aug 2, 2018 at 8:24 AM, François <francois.serman@corp.ovh.com> wrote:
On Thu, Aug 02, 2018 at 07:28:51AM -0400, Donald Sharp wrote:
François -
I am not aware of this being fixed. It just has not trickled up to a developers plate yet from what I can tell. Lot's of new goodies in 4.0 and 5.0 you should check them out and see if any of the new featrues are needed.
Thanks for your answer Donald. I don't think we *need* those features, but I was rather thinking about bugfixes, improvements, but most importantly, keeping up to date. I don't know how the "support" would work; for instance if a vuln was found, how deep [in older versions] would it be corrected? That's the main reason.
Regarding the "bug", I'll try to setup a minimal environment to check that.
Thanks :)
François
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev