+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] Cc: David McBride <[email protected]>; Fatih Degirmenci <[email protected]>; Frank Brockners (fbrockne) <[email protected]>; Tallgren, Tapio (Nokia - FI/Espoo) <[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 (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
