+1 and thanks for the proposal, Alex! Al
From: [email protected] [mailto:[email protected]] On Behalf Of Frank Brockners (fbrockne) Sent: Tuesday, September 26, 2017 4:44 AM To: Alec Hothan (ahothan); [email protected] Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed +1 – per what Alec mentioned below, the new tagging scheme is only a small change incremental change from the earlier plans, but offers a lot of flexibility moving forward. Frank From: Alec Hothan (ahothan) Sent: Montag, 25. September 2017 21:34 To: [email protected]<mailto:[email protected]> Cc: David McBride <[email protected]<mailto:[email protected]>>; Fatih Degirmenci <[email protected]<mailto:[email protected]>>; Frank Brockners (fbrockne) <[email protected]<mailto:[email protected]>>; Tallgren, Tapio (Nokia - FI/Espoo) <[email protected]<mailto:[email protected]>> Subject: [opnfv-tech-discuss] urgent euphrates git tags vote needed I would like to get a quick vote from any person that works directly or indirectly with code in OPNFV Please reply with -1, 0 +1 For using prefixed git tags for the Euphrates release: “opnfv-5.0.0” This is a slight change to the plan on record (which was to use “5.0.0”). This does NOT impact euphrates deliverables for participating OPNFV projects (git tags on stable/euphrates are applied by releng). The only externally visible effect is the naming of container tags for Euphrates official images in DockerHub will be named accordingly (e.g. “opnfv/functest:opnfv-5.0.0”). Everything else remains the same. If you’d like to know more, the rationale is described here: https://wiki.opnfv.org/display/releng/OPNFV+projects+and+OPNFV+release+versioning<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_releng_OPNFV-2Bprojects-2Band-2BOPNFV-2Brelease-2Bversioning&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=BnFOET7vVz-l5p-4mFgkGMGDJq3nJ0-m_uI0LdNLdQY&s=KH73GpdZq3OZ_SwuUHsjspzPst6HyDEYqE5lm4amMts&e=> (thanks for Fatih, David, Frank, Tapio for reviewing) In a nutshell, this adjustment is needed to prepare the path for proper continuous delivery support by projects. Any clarification/questions/discussion can be done over email or at the TSC or release meetings tomorrow. Thank You. Alec
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
