Hi Gerald, Looks like the tagging worked?
$ git tag -l brahmaputra.1.0 colorado.1.0 danube.1.0 danube.1.RC1 -Aric On Fri, Mar 31, 2017 at 5:31 AM, Kunzmann, Gerald <kunzm...@docomolab-euro.com> wrote: > Dear David, Aric, all, > > > > We had been trying to tag the release as described in the Wiki page, > however, with no success and the following error message: > > > > opnfv@souville-VirtualBox:~$ git clone > ssh://kunzm...@gerrit.opnfv.org:29418/promise > Cloning into 'promise'... > remote: Counting objects: 85, done > remote: Finding sources: 100% (13/13) > remote: Total 453 (delta 0), reused 451 (delta 0) > Receiving objects: 100% (453/453), 1.64 MiB | 530.00 KiB/s, done. > Resolving deltas: 100% (112/112), done. > Checking connectivity... done. > opnfv@souville-VirtualBox:~$ cd promise/ > opnfv@souville-VirtualBox:~/promise$ git fetch origin > > opnfv@souville-VirtualBox:~/promise$ git checkout stable/danube > > Branch stable/danube set up to track remote branch stable/danube from > origin. > Switched to a new branch 'stable/danube' > opnfv@souville-VirtualBox:~/promise$ git checkout > 92bd641d511dd52ab73122842f616ec2b6fc1c24 > Note: checking out '92bd641d511dd52ab73122842f616ec2b6fc1c24'. > > You are in 'detached HEAD' state. You can look around, make experimental > changes and commit them, and you can discard any commits you make in this > state without impacting any branches by performing another checkout. > > If you want to create a new branch to retain commits you create, you may > do so (now or later) by using -b with the checkout command again. Example: > > git checkout -b new_branch_name > > HEAD is now at 92bd641... Update doc structure to better fit release notes: > - There is no need for heading "Manual testing" - Update to user guide > abstract > opnfv@souville-VirtualBox:~/promise$ git tag -am "danube.1.RC1" danube.1.RC1 > opnfv@souville-VirtualBox:~/promise$ git push origin danube.1.RC1 > Counting objects: 1, done. > Writing objects: 100% (1/1), 174 bytes | 0 bytes/s, done. > Total 1 (delta 0), reused 0 (delta 0) > remote: Processing changes: refs: 1, done > To ssh://kunzm...@gerrit.opnfv.org:29418/promise > ! [remote rejected] danube.1.RC1 -> danube.1.RC1 (prohibited by Gerrit) > error: failed to push some refs to > 'ssh://kunzm...@gerrit.opnfv.org:29418/promise' > > > > > > Any idea what went wrong? > > Aric, could you kindly tag Promise for us? > > > > Best regards, > > Gerald > > > > From: opnfv-project-leads-boun...@lists.opnfv.org > [mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David > McBride > Sent: Dienstag, 28. März 2017 21:44 > To: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org>; > opnfv-project-leads <opnfv-project-le...@lists.opnfv.org> > Cc: Aric Gardner <agard...@linuxfoundation.org>; Raymond Paik > <rp...@linuxfoundation.org>; Rudy Grigar <rgri...@linuxfoundation.org>; > Tapio Tallgren <tapio.tallg...@nokia.com> > Subject: [opnfv-project-leads] [release][danube] revised schedule for > release > > > > Team, > > > > The TSC voted this morning to change the release date to Friday, March 31. > I will be updating the schedule on the wiki, but here is a summary of what > will happen this week. > > > > Note: on the release call this morning, I said that MS9 would be on > Wednesday. However, it was pointed out that finishing up the documentation > includes resolving and closing JIRA tickets, so I decided that it would make > more sense to schedule it on the same day as the documentation completion. > > Wednesday, March 29 > > MS8 - end of formal testing and data collection > > Thursday, March 30 > > MS9 - JIRA cleanup > MS10 - complete documentation > > Friday, March 31, 3 p.m. PDT > > PTLs tag projects > Note that we are using an "RC" tag, initially, for this release. You can > apply this tag while you are completing your final reviews, etc., then once > you are certain that you are done, then you can apply the "1.0" tag. > > David > > > > -- > > David McBride > > Release Manager, OPNFV > > Mobile: +1.805.276.8018 > > Email/Google Talk: dmcbr...@linuxfoundation.org > > Skype: davidjmcbride1 > > IRC: dmcbride _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
