[cmaster-next] Today's Agenda
RC2.0 - Where we are Branching RD/RT EVPN. Anything else we need to add to the agenda? doanld
Meeting Notes: 1) We discussed the name and the top three choices from the survey were: Pigeon, Phoenix and Free Range Routing. Due to concerns brought up by trademark and similarities between Pigeon and Phoenix to other projects, Free Range Routing was selected. I know it's been a long hard process and I'd like to thank everyone on their input to the naming process! 2) RC2.0 - Discussion of individual bugs and what was left to do. We are tracking RC2.0 via the github issue tracker. Please use that to open up bugs. Just a few issues are left. -> We are going to startup a patchworks shortly here, no current ETA. 2) Branching. The branching diagram was discussed and the decision was to implement the diagram and revisit it again in 4-6 months to see if it needs to be tweeked. 3) We will be having a meeting on 12/20 and skip 12/27 meeting to pick right back up in Early January. donald On Tue, Dec 13, 2016 at 8:34 AM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
RC2.0 - Where we are
Branching
RD/RT
EVPN.
Anything else we need to add to the agenda?
doanld
Hi Donald, all Le 14/12/2016 à 14:13, Donald Sharp a écrit :
Meeting Notes:
1) We discussed the name and the top three choices from the survey were: Pigeon, Phoenix and Free Range Routing. Due to concerns brought up by trademark and similarities between Pigeon and Phoenix to other projects, Free Range Routing was selected. I know it's been a long hard process and I'd like to thank everyone on their input to the naming process! And the acronym is FRR: i.e. Fast Re-Route ;-)
Olivier _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
participants (2)
-
Donald Sharp -
olivier.dugeon@orange.com