Hi Jessica, For vnfsdk-pkgtools, I think the 'beijing' tag should be applied to the current master tip version. The 'release/mercury' came from pre Amsterdam release, it came from Open-O.
Best Regards, -Lianhao -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jessica Wagantall via RT Sent: Friday, June 8, 2018 7:10 AM To: [email protected] Cc: [email protected]; [email protected] Subject: [onap-discuss] [ONAP Helpdesk #57038] beijing repo branching Dear Gildas All branches needed to be renamed from "Beijing" to "beijing" are now renamed. All "beijing" branches have been created and tagged for all repos which my script detected no tag at all. These have been branched of from the tip of master. (See attached list "all-no-tags") All "beijing" branches have been created for the repos which had release tags. The branching point was the latest tag available which should match the last version released. (See attached list "all-tags") From this particular list, I want to mention few important cases which my script detected: ------has an 2.0.0-ONAP tag already (probably applied by the tech team). Couldn't move this tag to the tip of the beijing branch dcaegen2-collectors-ves ------very old last release (Nov). beijing branch is as old as the amsterdam branch. I can help FF if the team wants holmes-common holmes-dsa holmes-engine-management holmes-rule-management ------very old tag detected "release/mercury". beijing branch is as old as the amsterdam branch. I can help FF if the team wants vnfsdk-lctest vnfsdk-pkgtools Please let me know for your comments. Thanks! Jess On Thu Jun 07 19:02:38 2018, jwagantall wrote: > Dear Mike.. > > Sorry i noticed this message a little bit late. I had created the > beijing branch for oom from the latest tag available. But I can always > remove it and re-create it from whichever point you need. > > Just let me know if I should proceed removing it. > > Thanks! > Jess > > > On Thu Jun 07 16:33:01 2018, [email protected] wrote: > > > Hey Jessica, > > > > > > We have a bit of a glitch in releasing and tagging all at once. > > > There > > > is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on > > > the OOM Beijing branch, but can only be tested and merged once > > > beijing branches are created for the repos referenced within this > > > patch. > > > Is it possible to do this in two stages so we can make this happen? > > > > > > Thanks, > > > Mike. > > > > > > On 6/7/18, 3:28 PM, "[email protected] on behalf > > > of Jessica Wagantall via RT" <[email protected] > > > on behalf of [email protected]> wrote: > > > > > > Thanks so much for gathering this information Gildas! > > > This is a great list! > > > > > > I have few questions: > > > > > > - Are the teams ok branching from the latest tip of master? (This > > > will make it easier on my script) > > > - Do the teams want me to tag the tip of the beijing branch with > > > "2.0.0-ONAP" tag? > > > > > > Thanks! > > > Jess > > > > > > On Thu Jun 07 15:23:43 2018, [email protected] wrote: > > > > Hi Helpdesk, > > > > > > > > Following TSC discussion on June 7, find in attachment the > > > > status of all ONAP repo and their need for a "beijing" branch. > > > > You will see that a lot has already been done. > > > > > > > > Thanks, > > > > Gildas > > > > > > > > [HuaweiLogowithName] > > > > Gildas Lanilis > > > > ONAP Release Manager > > > > Santa Clara CA, USA > > > > [email protected] > > > > Mobile: 1 415 238 6287 > > > > > > > > > > > > _______________________________________________ > > > onap-discuss mailing list > > > [email protected] > > > https://lists.onap.org/mailman/listinfo/onap-discuss > > > > > > > > > This message and the information contained herein is proprietary > > > and confidential and subject to the Amdocs policy statement, > > > > > > you may review at https://www.amdocs.com/about/email-disclaimer > > > <https://www.amdocs.com/about/email-disclaimer> _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
