Okay, thanks.

Lou

On 01/22/2016 07:18 AM, Donald Sharp wrote:
> Lou -
> 
> I need to push it out this morning actually.
> 
> donald
> 
> On Fri, Jan 22, 2016 at 7:12 AM, Lou Berger <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Just a FYI to the list. We've posted a fix to the crash (patch to
>     our patch) on our github repo and Donald has included it in his test
>     branch.
>     Lou
> 
> 
> 
>     On January 20, 2016 6:53:03 AM Lou Berger <[email protected]
>     <mailto:[email protected]>> wrote:
> 
>         We just learned of this crash this AM. Will let you know what we
>         find...
> 
>         Lou
> 
> 
>         On January 20, 2016 6:36:33 AM "Martin Winter"
>         <[email protected]
>         <mailto:[email protected]>> wrote:
> 
>             On 19 Jan 2016, at 7:20, Donald Sharp wrote:
> 
>                 Status of Current Master:
>                    -> Martin has seen a crash on this tree?  Martin to send
>                 information
>                 about this crash.
> 
> 
>             Correction, that’s not what I said.
>             I’m not aware of any crash based on the master branch (as of git
>             eae18d16)
> 
>             You were talking about upcoming merges of Lou Berger’s code
>             and I
>             mentioned
>             that I’m aware of a crash in Lou’s code. But that’s not yet in
>             master and would
>             not stop a release based on current master
> 
>             - Martin
> 
> 
>                 We want to Roll a release before next patch series goes
>                 in.  Donald and Paul to work on this.
> 
>                 Status of Current Patch Series:
>                   -> Currently being applied now.  Currently working
>                 through Lou
>                 Berger's
>                 30 patches to apply
>                   -> Timo's Patch 1786 -> enum for linktype belongs in a
>                 different
>                 header.   Donald will rework that patch and apply Timo's
>                 series.
>                   -> Cumulus Patches next to be applied.
> 
>                 Multi-topology Routing:
>                   -> RFC 4915
>                   -> Discussion of some small implementation details,
>                          VRF's, Multi-Instance OSPF were discussed
>                          LSA's would contain multiple costs for links
>                 limited by
>                 number
>                 of TOS/DSCP bits.
>                          Jafar needs to do a bit more work on this
>                 before it can be
>                 submitted.
> 
>                 Use of a different CR tool:
>                    -> Gerrit proposed by Vincent
>                         Various pro's and con's discussed
>                         Vincent to send a workflow and quick intro to
>                 Gerrit, please
>                 look
>                 at it for next meeting.
>                    -> If you are interested please send a proposal to
>                 the list.
> 
>                 Traffic Engineering Patch from Olivier
>                    -> Bunch of issues have been fixed
>                    -> Need some vtysh advice, please send question to alias.
>                    -> Issue with OSPF point-to-point to discuss?  Resend
>                 question to
>                 alias.
>                    -> BGP Link State patch for traffic engineering purposes
>                         Need an api for bgp to talk to other protocols. 
>                 Zebra is the
>                 logical choice, but an API should be developed where
>                 interested
>                 parties can
>                 register with zebra.
> 
>                 Netconf/Yang support
>                    -> Patches accepted, but a generic layer for all cli
>                 support needs
>                 to
>                 be developed.
> 
>                 Thanks for Don Slice taking the notes!
> 
>                 donald
>                 _______________________________________________
>                 Quagga-dev mailing list
>                 [email protected]
>                 <mailto:[email protected]>
>                 https://lists.quagga.net/mailman/listinfo/quagga-dev
> 
> 
>             _______________________________________________
>             Quagga-dev mailing list
>             [email protected] <mailto:[email protected]>
>             https://lists.quagga.net/mailman/listinfo/quagga-dev
> 
> 
> 
> 
>         _______________________________________________
>         Quagga-dev mailing list
>         [email protected] <mailto:[email protected]>
>         https://lists.quagga.net/mailman/listinfo/quagga-dev
> 
> 
> 
> 


_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to