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 "new 1.4" that was mentioned in the > session? > > However, as Rob Shakir mentioned in the session, there are other ways > to do fixes / enhacements than branching a single module. You can add > new functionality with augment and make changes with deviations. >
So we could potentially result in a cleaner set of base model versioning but augments and deviations that will need somewhat of it's own branch versioning now. I often find that consumers/clients make quite a few assumptions and expectations when one supports model version X (w/o the realization that it is X+/- for various reasons) We'll have a namespace problem which will result in namespaces being inserted (and removed at later dates) which ultimately has an impact on clients Possibly a better middle ground but think there are still considerations here as well as to the overall impact of this approach /ebben _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
