Hi all Than Ha, I got the same question on another thread so thank you for the clarifications.
Here is my feedback. If SM projects are affected by the branch lock of Managed projects because of Gerrit limitations, I think this is problematic, not only from a schedule standpoint. If I am not mistaken, Jenkins releng macros are only available on predefined branches. This means Neon CI/CD can only be installed there and new changes can really be tested in the stable/neon branch. This really complicates the integration work. I noticed also that target dependencies versions are stabilized 1 or 2 days just before the branch lock. Afterwards, there are a couple of weeks where SNAPSHOT and non-SNAPSHOT versions continue to coexist. I perfectly understand that not all project and subproject versions can be documented. But since the release target doc includes non-snapshot and snapshot versions, even with nexus, it is complicated in such conditions to know which subproject (e.g. mdsal.binding.model = 1.2.6) version must be used when its version is non-aligned with the parent project version (e.g. mdsal.binding-parent =3.0.6). In that case, the branch locks prevents SM projects from correcting the pom configuration without the help of a super committer. What the point of having a 2 * +2 review to correct an obviously non-working configuration ? (More generally, I would say what is the point of having a 2 * +2 but that is another debate ? ☺ ) Hope this helps BR Guillaume From: [email protected] [mailto:[email protected]] On Behalf Of Thanh Ha Sent: mardi 19 février 2019 17:50 To: Christine Cc: Release; discuss Subject: Re: [release] [OpenDaylight Discuss] Can't do merge in snmp4sdn stable/neon branch Hi Christine, What I would do is prepare your patch so that: * it passes Jenkins * has no merge conflicts * +2 the patch by a snmp4sdn committer Then any of the super committers [0] can submit the patch for you during stable/neon code freeze. Because the way Gerrit blocks branches we cannot unblock for only a single project so this is the best path. Reply here with a list of patches you'd like merged once the above conditions are met and we can merge your patch for you. Hope this helps, Thanh [0] https://docs.opendaylight.org/en/latest/release-process/super-committers.html#id1 On Mon, Feb 18, 2019 at 9:45 PM <[email protected]<mailto:[email protected]>> wrote: Thanks Anil Luis. Is Adam the release manager? Would you help to unlock snmp4sdn stable/neon branch, then I can add snmp4sdn to distribution repo. Thank you. Christine From: Anil Belur [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, February 19, 2019 7:50 AM To: Luis Gomez Cc: 謝宜玲; OpenDaylight Discuss; Release Subject: Re: [OpenDaylight Discuss] [release] Can't do merge in snmp4sdn stable/neon branch On Tue, Feb 19, 2019 at 9:10 AM Luis Gomez <[email protected]<mailto:[email protected]>> wrote: Hi Anil, AFAIR Self-Managed projects are not affected by milestones, so I think it should be OK to open the branch. ah sorry, forgot snmp4sdn is SM project. - Anil -- 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient. _______________________________________________ release mailing list [email protected]<mailto:[email protected]> https://lists.opendaylight.org/mailman/listinfo/release _________________________________________________________________________________________________________________________ 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.
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
