Donald,
I just sent a reply and acked a very important fix for pimd. Not
sure why I don't see the patch on patchwork list
Also, I made a couple of changes to my original ospfd fix patch. I'm
about to send it now.
After more testing I found that an assertion that I put in the patch
is better replaced
by code that handles the situation and moves on.
Regards,
Jafar
On 4/21/2016 3:55 PM, Donald Sharp wrote:
Donald, Martin, Lou, Jafar, David, Vincent, Philippe, Balaji
Donald - several crash fixes in ripd, isisd, etc
Should we roll the fixes out soon?
Martin- more coming soon? If not, we should get a bugfix
release out
Jafar - wait 2-3 weeks for fixes based on these changes?
Lou - process for getting them applied and out?
Bugfix release in 2-3 weeks make sense, just needs process
Donald - Apply crash fixes to master and have Martin test
Martin - another branch or master?
Donald - prefer master rather than branching?
Lou - should this use branching strategy laid out previously?
Additional branching was Paul's desire
Prefer to do what makes sense
Donald - second thought - use this to test out branching strategy
Use proposed branch for the patches
Can then apply the results to discussions with Paul
Lou will send out definitions of roles to the list
Martin - Address freeBSD issue previously sent to the list?
Worried could be serious to any BSD implementation
Donald - if someone is interested and worried, they can deal
with it
Lou - Paul(Non Jakma) ? who works on freeBSD says will work on
it if trips over it
Take 3 branch
Paul didn't like what we did and still under discussion
RFC compliance in OSPF
David said IETF OSPF WG had a laugh at our expense for this
behavior
Paul submitted a patch but no one has evaluated it yet.
Plan to go with H bit instead as RFC draft states
If a knob, need to use it turn off rfc compliance rather than on
More comments from Paul needs to be addressed, but have been
too busy to respond
David - need to get Take-3 merged and then fix stuff if broken
Donald - Process has become so slow it appears that we'll
never get caught up
After the 100 patches pending, another 250 pending
Discussion of the sequence number issue with our
implementation
Lou - push this to a proposed branch rather than operating
over the take-3 branch?
Use the process as defined - proposed-7 for bugfix,
proposed-8 for the take-3 branch?
Can Vincent push it since the process says the
submitter can't push their own?
Too busy at this point
Put on the list and get access for someone if
needed (David?)
Who can edit the list (commit access?)
David believes he can request and then needs
to have it acked
Lou - will push out L2 and L3 vpn code in the next couple of weeks
Will need to discuss where this gets targeted in the proposed
branches
Won't tie in to 6Wind vrf pieces at this time - default only
Donald mentioned that we were working on MPLS
Lou asked if our BGP changes will conflict with theirs
(not clear)
May not be significant since we're targeting
different use-cases
Martin said Vivek/Daniel should talk to someone (?)
concerning LDP since pretty far down that road
Lou interested in how we're managing labels and tied
to prefixes
Currently static labels - want LDP to make it functional
Donald will try to get the code exposed in the next
couple of days
David - Discussion on coding style consistency
Sending email on reasonable consensus on response
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
