<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Ubuntu">Hi Donald,</font></p>
<p><font face="Ubuntu">A couple of comments.</font></p>
<p><font face="Ubuntu">Regards</font></p>
<p><font face="Ubuntu">Olivier</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 17/01/2017 à 19:29, Donald Sharp a
écrit :<br>
</div>
<blockquote
cite="mid:CAK989ydnMwcTAU+GamOrVupOb8GLrcU7dhoDa8VT=bNLDCGypw@mail.gmail.com"
type="cite">
<pre wrap="">1) Status - We believe we are really close to rc1 status. Need a
couple of bug fixes now. We've updated the issues page if you are
interested.
2) RD/RT cli discussion.
Discussion around the RD/RT document
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/1w_ie2tNXCgn0N3ZNFGYTK6lJkwMmk_XN5yz33MMNNqM/edit#">https://docs.google.com/document/d/1w_ie2tNXCgn0N3ZNFGYTK6lJkwMmk_XN5yz33MMNNqM/edit#</a>
Top of the document has the cli we have started converging on, please
review and discuss further if you have questions.</pre>
</blockquote>
Concerning the last part of the discussion about CLI. I would add
one more things to the way CLI could evolve.<br>
<br>
Suppose we are at release N. For next major release N+1, we decided
to change/modify/delete some OLD CLI and introduce a NEW one. A
smooth way to evolve could be to deprecated the OLD CLI while
introducing the NEW LCI. this way, the code continue to support the
OLD CLI, but with a Warning saying that this command will be
deprecated in next release, to let users time to adapt their
configuration. Then, in release N+2, the OLD CLI is removed.<br>
<br>
I agree that this introduce more code (need to support both OLD and
NEW CLI) that in some case will be not possible, but could be safer
for users. If accepted, the rule is to tag OLD CLI code with a
special //DEPRECATED comment to know that this will be remove in
future release. <br>
<blockquote
cite="mid:CAK989ydnMwcTAU+GamOrVupOb8GLrcU7dhoDa8VT=bNLDCGypw@mail.gmail.com"
type="cite">
<pre wrap="">
3-6) We ran out of time.</pre>
</blockquote>
Hope next meeting we have time to discuss the Pull request process.<br>
Can you put it on top of the agenda for next meeting as this is the
second time we ran out of time ?<br>
<blockquote
cite="mid:CAK989ydnMwcTAU+GamOrVupOb8GLrcU7dhoDa8VT=bNLDCGypw@mail.gmail.com"
type="cite">
<pre wrap="">
Daniil Baturin joined us from VyOS to discuss our fork and where we
plan to go. We hope to see more from him in the future!
thanks!
donald
On Tue, Jan 17, 2017 at 7:35 AM, Donald Sharp
<a class="moz-txt-link-rfc2396E" href="mailto:sharpd@cumulusnetworks.com"><sharpd@cumulusnetworks.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">11 am EST ( 4pm UTC ) - If you would like an invite please unicast me.
Agenda:
1) Last Week status
2) RD/RT - cli finish
3) Olivier's Proposal for Pull Requests
4) Functional changes needed for VRF
5) Formating changes
6) If you have something you want to add to the agenda, let me know!
Thanks!
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
frr mailing list
<a class="moz-txt-link-abbreviated" href="mailto:frr@lists.nox.tf">frr@lists.nox.tf</a>
<a class="moz-txt-link-freetext" href="https://lists.nox.tf/listinfo/frr">https://lists.nox.tf/listinfo/frr</a>
</pre>
</blockquote>
<br>
</body>
</html>