On Nov 09 14:42 PM, Martin Bjorklund wrote:
> > The
> > point of requirement 1.4 was to say that the DT felt previous versions
> > of modules needed to support fixes without bringing in elements from head.
>
> I think this means that you require branching.
>
> But is this still the point of the
Joe Clarke wrote:
> On 11/8/18 16:46, Martin Bjorklund wrote:
> > Hi,
> >
> > After the session today, it seems to me that one fundamental
> > requirement (or non-requirement) is missing. How much branching does
> > the solution have to support? The current solution (6020/7950) and (if
> > I
Hi,
After the session today, it seems to me that one fundamental
requirement (or non-requirement) is missing. How much branching does
the solution have to support? The current solution (6020/7950) and (if
I understood Rob Shakir correctly) also openconfig have linear
versioning *per module*.
The netmod YANG versioning design team has updated the requirements
draft based on comments received at IETF 102 as well as some individual
discussions. Highlights include:
* Definition of "non-backwards-compatible"
* Clarification on what clients should do with backwards-compatibly
changed
