That is correct. The opnfv.x.y.z are actually tags managed by the OPNFV release not by project owners. They are always on stable branches. The x.y.z tags are always on master and controlled by project owners (if they want to have such tags as they are optional).
Thanks Alec From: "Yujun Zhang (ZTE)" <zhangyujun+...@gmail.com> Date: Monday, September 25, 2017 at 5:55 PM To: "Alec Hothan (ahothan)" <ahot...@cisco.com>, "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed I had a quick look at the wiki page and try to understand the rationale behind proposal. If I understand it correctly, it is like - opnfv-x.y.z to sync with OPNFV official releasing cycle, i.e. Danube, Euphrates (opnfv-5.y.z). - (optional) x.y.z for project intermediate release which is managed by each project. Please correct me if anything wrong. I would vote +1 based on the understanding above. On Tue, Sep 26, 2017 at 3:34 AM Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote: 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 opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss -- Yujun Zhang
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
