Hi Eric, To help the discussion on tagging, I would like to indicate that tagging is made in multiple locations. From what I know I see:
1) Tagging at the repository level: that was done by LF when we had the first release of Amsterdam on Nov 16 and then later for the maintenance release in January. 2) Tagging the docker images: As Helen pointed out, we have been working with numerous people and LF on this. Jira Ticket is here<https://jira.onap.org/browse/CIMAN-132>. 3) We also have the Manifest files that record the version of the Binary artifacts<https://git.onap.org/integration/tree/version-manifest/src/main/resources/java-manifest.csv> and Docker artifacts<https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv> once they are released 4) Not familiar with the file<https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env?h=amsterdam> you have shared in the Demo repo, but I guess this file is pulling information from the above. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Yunxia Chen Sent: Wednesday, February 28, 2018 10:41 AM To: eric.deb...@orange.com; onap-tsc@lists.onap.org Subject: Re: [onap-tsc] tagging issues Hi, Eric, I agree with you: this indeed a concern. Right now, Gildas, Ran and Gary are working with Linux foundation on this one and hopefully to get a solution very soon. And I also expect a stable master branch build, meaning we could run some basic sanity testing, more specifically, passing health test, running the automated vFW and vLB use case. And each day, we could tag what have successfully passed above testing. Regards, Helen Chen From: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Eric Debeau <eric.deb...@orange.com<mailto:eric.deb...@orange.com>> Date: Wednesday, February 28, 2018 at 10:09 AM To: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: [onap-tsc] tagging issues Hello We still have some problems in the ONAP versioning/tagging. In the Amsterdam version environment file (https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env?h=amsterdam) , there is still one project based on master branch. The Docker tags are not all aligned (some start with v, other with a figure) and all there is still missing a lot of latest tags on Docker images under the DockerHub repo. As we will jump in Beijing and then Casablanca, Dublin, we should have a latest-stable release to avoid to manage various branches and the version namings. Best Regards Eric _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
