Thanks Trevor,
The latest wiki page is a lot less confusing (thanks Aric!).
I still have a doubt on the tag itself (opnfv-6.0.0). Should we still tag it
ourselves directly?
I was just wondering if we couldn’t simply have the project leads identify the
release using the tag instead of having to hardcode the hash in a releng file
(for every maintenance release as well)?
For example in my project case, I had to add the bold part:
$ cat nfvbench.yaml
---
project: nfvbench
project-type: tools
release-model: stable
releases:
- version: opnfv-6.0.0
location:
nfvbench: c8402089ad8686a16ad08ce6c6e16a14c3144d64
branches:
- name: stable/fraser
location:
nfvbench: 34c00544f7f7dbfa49bbdcd83eca2936b60826c7
release-notes:
http://docs.opnfv.org/en/stable-fraser/submodules/nfvbench/docs/release/release-notes/release-notes.html
Wouldn’t it be simpler that I just had to add the “opnfv-6.0.0” tag at the
proper commit on stable/fraser, and that would trigger the build of my
containeir “nfvbench:opnfv-6.0.0”?
From the tag name, releng should be able to find very easily the exact hash
from git.
Thanks
Alec
From: Trevor Bramwell <tbramw...@linuxfoundation.org>
Date: Thursday, April 26, 2018 at 2:26 PM
To: "Alec Hothan (ahothan)" <ahot...@cisco.com>
Cc: Aric Gardner <agard...@linuxfoundation.org>, "Beierl, Mark"
<mark.bei...@dell.com>, David McBride <dmcbr...@linuxfoundation.org>,
opnfv-project-leads <opnfv-project-le...@lists.opnfv.org>, TECH-DISCUSS OPNFV
<opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [release][documentation][fraser] MS9 - final
documentation (TODAY)
Hi Alec,
On Thu, Apr 26, 2018 at 04:07:23PM +0000, Alec Hothan (ahothan) wrote:
I tried to read through the wiki and had some questions…
https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Fraser
I just cloned releng and did not find any yaml file that has a
“releases:” section yet, is it normal or am I the first to do? The
example in the wiki is still pretty confusing:
I don't think any of the releases files have been merged in yet[1], which
is why you're not seeing the 'releases:' section yet.
1. Why is the branches: section mentioning stable/euphrates ?
Shouldn’t it be stable/fraser instead (like all the yaml files have)?
Yep, that should be 'stable-fraser'. I've updated the wiki.
2. Could the wiki explain what is the role of a branches: and role of
releases: sections?
All the sections should be documented here[2] (adding the link to the
wiki), but please let me know if you see one that's missing.
(I'm aware the formatting is off for subfields.)
3. Should we put the same SHA1 in branches and releases? If yes why the
duplicate?
No. This is a common mistake I keep seeing. The branch sha1 does not
need to change as that is the location of where the stable branch
started. Finding the current commit of stable/fraser can easily be done
by looking at the repo.
As a note, the other common mistake I keep seeing is people not using
the commit _from_ stable/fraser, but master.
Great questions!
Regards,
Trevor Bramwell
[1]
https://gerrit.opnfv.org/gerrit/#/q/project:releng+path:%255Ereleases/fraser/.*
[2]
http://docs.opnfv.org/en/stable-fraser/submodules/releng/docs/release/release-automation.html#release-file-fields
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
