Oliver, Ok, make sense. When can we expect the master branch to be in a state where only patches with well defined scope will be pushed?
Thanks, Alexis On Apr 6, 2017, at 4:45 PM, SPATSCHECK, OLIVER (OLIVER) <spatsch at research.att.com<mailto:spatsch at research.att.com>> wrote: I think there are two phases to this. We have explained this before but I am not sure if everybody has heard this. The current ONAP code base is based on our ECOMP code base from Sep. 2016. We are currently in the process of getting it updated to our current internal version. That?s a lot of code we will commit by 5/5 and we are likely to break ONAP in the master branch occasionally until this is complete. That?s the reason we have a 1.0.0 branch and the master branch has moved on to 1.1.0 . So to speed up the code sync we told our developers to be brief on the commit messages and commit in larger junks then usual. After we are caught up (5/5) we will start tracking commits towards more detailed JIRA tickets. If we did that right away it would substantially delay the catch up phase based on the man power required. So if you are looking for a stable version please use the 1.0.0 branch that?s what the demo heat template uses too. Always ope to suggestions. Oliver On Apr 6, 2017, at 4:35 PM, FREEMAN, BRIAN D <bf1936 at att.com<mailto:bf1936 at att.com>> wrote: *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Alexis, What would be the best mechanism to communicate this type of thing ? As we push our Feb and June 2017 code updates into ONAP repositories there will be more version changes of external open source ? Would a notice on this list be enough or should there be another tool/process used ? We are open to what would be better for the community ? Brian -----Original Message----- From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Alexis de Talhou?t Sent: Thursday, April 06, 2017 3:49 PM To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: [onap-discuss] Upgrade from ODL Beryllium to Boron Hello guys, I?ve seen that recently you?ve upgraded ODL?s version. APPC https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Da41533fb0a79e7399f7bf0ba53a1211c67e50d04&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=yqEiYEqq3lumI3bdXWz4Rxa5GynG3EX_2qUzZvFrOvo&e= https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dcommit-3Bh-3Dda976a9c10cca4249e97f6629eb17cd52a7e4955&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=0xrdhJsf90kPIdSWhe-l0tULo2Ve3nyPyNnuVInmDRM&e= SDNC https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2905_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=vxs3n-9zqJjaSFCFICdqvEm505UT6YK3cOTbvS0bIvY&e= https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2907_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=4p__SxAqsG_N6wlgXGfZdFX-A-DyYyBMymL6SqHJeXY&e= (plugins) https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_2901_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=3588Z0vornh0qWGD9HcNrNdKafzbni2w6hTz6VAoyLM&e= (core) ... This is great. But please, next time, do advertise change like this, so other don?t spend cycles looking into this? Also, if possible, write accurate commit message, so one can track changes from the git log. Regarding the commit message, here are awesome guideline: https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opendaylight.org_view_BestPractices_Commit-5FMessages&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=-io3OaDPAIuXe_BguMJ_zalYEuzBS52c-BgL8i_q0MA&e= Thanks, Alexis _______________________________________________ onap-discuss mailing list onap-discuss at lists.onap.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=q7BeHKfy83yZiEdPGNXxhzrr_9ZnDW-2x_YZ3AZza40&s=nzNqEfODOX4QdGrDp8w55SCZExDDcCFPTULEsVVF1fk&e= _______________________________________________ onap-discuss mailing list onap-discuss at lists.onap.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=9iyuArzgyekj47PZSPfIijI2cSHsUJtAlcTA0X_udNI&m=wNgbDgsZiQxEQNBpTpNZxS0Hopji1qrvlb-A5sRDOnY&s=56XxQd3ZiXBUpDRWQd7wiJg5wwuJ65mBvxZSnptSPV0&e= _______________________________________________ onap-discuss mailing list onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170406/ded17e01/attachment-0001.html>
