Re: [release] SM projects status
Guillaume Lambert
I guess we have here a confusion between mdsal binding-parent and mdsal binding.model.
toggle quoted message
Show quoted text
My point was that they use different revisions and that binding.model versions are not documented anywhere, nor the documentation nor the wiki. But fair enough, what I understand from your answers is that mdsal binding.model version should be aligned with mdsal binding-parent version 3.0.6 since mdsal is now released. I found confirmation on nexus that version 1.2.7-SNAPSHOT is not aligned with binding-parent 3.0.6 but 3.0.7-SNAPSHOT probably to prepare Neon SR1. According to nexus, mdsal binding.model version 1.2.6 is OK https://nexus.opendaylight.org/service/local/repositories/opendaylight.release/content/org/opendaylight/mdsal/binding/model/ietf/rfc6991-ietf-yang-types/1.2.6/rfc6991-ietf-yang-types-1.2.6.pom Same things for ietf-access-control-list 0.13.6 and iana-if-type 1.0.6. So it is now fixed in change 80409. https://git.opendaylight.org/gerrit/#/c/80409/ Thank you both for your feedbacks. BR Guillaume PS: About the branch locking, I see there is another thread started with SNMP4SDN so I will joint it. -----Original Message----- _________________________________________________________________________________________________________________________ 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. |
|