Re: [opnfv-tech-discuss] [opnfv-tsc] Hunter release MS8 - 11, week of May 6 #hunter #release

I imagine that the reason that you're seeing links from master is that people simply copied the links that they used for the preliminary documentation requirement at MS6, rather than get the links from the branch. David On Fri, May 10, 2019 at 11:57 AM David McBride wrote: > Alec, > > That's a

Re: [opnfv-tech-discuss] [opnfv-tsc] Hunter release MS8 - 11, week of May 6 #hunter #release

Alec, That's a good point. We used to just collect links for final documentation, but then we added the preliminary documentation requirement at MS6 a few releases back, and simply copied the idea of link reporting. However, now that I think about it, it probably only makes sense to do that at

Re: [opnfv-tech-discuss] [opnfv-tsc] Hunter release MS8 - 11, week of May 6 #hunter #release

David, I would like to point out that practically all links provided in the tables point to master branch, for example: https://git.opnfv.org/fuel/tree/docs when it should be most likely be https://git.opnfv.org/fuel/tree/docs?h=stable%2Fhunter Unless it is implicit that all these links

[opnfv-tech-discuss] [opnfv-8.0.0] Fuel Release Artifacts

Hi, Fuel release information: 1. Fuel artifacts: - git tag [1]; - documentation [2, 3, 4]; NOTE: Although we do not release Armband like we did in the previous releases, all AArch64 specifics are now upstream in OPNFV Fuel as well, so starting with 7.0.0, the Fuel artifacts can be used for

Re: [opnfv-tech-discuss] Hunter release MS8 - 11, week of May 6 #hunter #release

Team, Hunter 8.0 release is today. - I was late in posting the tagging instructions ; however, they have not changed since the last release. So, if you have not yet tagged your repo for Hunter 8.0, please do

Re: [opnfv-tech-discuss] status of Hunter release #hunter #release

Amar has collected feedback from PTLs here: https://wiki.opnfv.org/display/SWREL/Hunter+Release+Key+Updates. Brandon is working on the Hunter messaging and will be discussing that in the next TSC meeting. As is often the case with a releease, we are still reaching out to the projects to make