I think it could hurt only if you select 2017.09 as tag. I precise pbr compares version (eg 5.0) and tags then it would break the python package.
Cédric 2017-09-11 17:20 GMT+02:00 Alec Hothan (ahothan) <ahot...@cisco.com>: > > > Fatih mentioned that changes in F would be in a different repo after the > reorganization of the releng repo – so branching releng would technically > not be needed for Euphrates? > > In any case, it does not hurt to tag (I was surprised tags were not used > more often in OPNFV repos to mark internal versions…) > > > > > > Alec > > > > > > > > > > From: <opnfv-project-leads-boun...@lists.opnfv.org> on behalf of "Beierl, > Mark" <mark.bei...@dell.com> > Date: Monday, September 11, 2017 at 6:31 AM > To: Alexandru Avadanii <alexandru.avada...@enea.com> > Cc: opnfv-project-leads <opnfv-project-le...@lists.opnfv.org>, Cedric > OLLIVIER <ollivier.ced...@gmail.com>, "opnfv-tech-discuss@lists.opnfv.org" > <opnfv-tech-discuss@lists.opnfv.org> > Subject: Re: [opnfv-project-leads] [opnfv-tech-discuss] [release][euphrates] > stable branch window > > > > +1. Would not want changes to the opnfv-docker.sh script for F to impact > building of E maintenance releases. > > > > Regards, > > Mark > > > > Mark Beierl > > SW System Sr Principal Engineer > > Dell EMC | Office of the CTO > > mobile +1 613 314 8106 > > mark.bei...@dell.com > > > > On Sep 11, 2017, at 09:26, Alexandru Avadanii <alexandru.avada...@enea.com> > wrote: > > > > Hi, > How about tagging releng, without branching it? > > Alex > > > -----Original Message----- > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss- > boun...@lists.opnfv.org] On Behalf Of Cedric OLLIVIER > Sent: Monday, September 11, 2017 7:51 AM > To: David McBride > Cc: opnfv-project-leads; TECH-DISCUSS OPNFV > Subject: Re: [opnfv-tech-discuss] [release][euphrates] stable branch window > > Hello, > > Could you please confirm that no stable/euphrates branch will be created for > releng again? > Else we are obliged to select a specific git commit id to build our Functest > stable containers which is not the best way. > I precise Functest depends on the opnfv python package which is hosted by > releng (https://git.opnfv.org/releng/tree/modules). > > Cédric > > 2017-09-09 1:24 GMT+02:00 David McBride <dmcbr...@linuxfoundation.org>: > > Reminder... > > The stable branch window closes as of MS7, one week from today, on > September > 15 at 12 p.m. (PT). PTLs - please contact Aric as soon as you're ready > to branch. Aric will branch any projects that have not already been > branched on Sept 15. > > Let me know if you have any questions. > > David > > On Tue, Aug 29, 2017 at 3:23 PM, David McBride > <dmcbr...@linuxfoundation.org> wrote: > > > Team, > > As you know, MS6 was this past Friday, Aug 25. In addition to the > requirements associated with MS6, this milestone also marks the > opening of the stable branch window, which subsequently ends with MS7 on > > Sept 15. > > > This means that PTLs may request to branch their project any time > before Sept 15. Note that I erroneously told the release meeting > this morning that PTLs may create their own branch. That's not the > case. Instead, please contact Aric (copied) and request that he create the > > branch for you. > > > Also, as a reminder, we have changed the version number format as of > the Euphrates release. > > 5.0.0 - Euphrates initial release version > 5.1.0 - Euphrates SR1 > 5.2.0 - Euphrates SR2 > > Let me know if you have any questions. > > David > > -- > David McBride > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride > > > > > > -- > David McBride > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
