Gildas, Jessica,
I think we are OK with closing this issue. Cloning across the entire ONAP can be managed per/developer and is a lower priority these days under our other initiative.
Thank you for your work.

https://lf-onap.atlassian.net/browse/INT-373

----Original Message----
From: Jessica Wagantall via RT onap-helpdesk@rt.linuxfoundation.org
Sent: Monday, February 5, 2018 17:04
To: gildas.lanilis@huawei.com
Cc: Michael O'Brien <Frank.Obrien@amdocs.com>; kpaul@linuxfoundation.org; probb@linuxfoundation.org
Subject: [ONAP Helpdesk #50270] Amsterdam Missing branches

Dear Gildas,

Do we need to revive this discussion?
As mentioned before we took the holiday break, I created the amsterdam branch for those repos which actually made a Nexus/Nexus3 publication.

If a repo that did not made a release needs an amsterdam branch, it is still under the committer's group power to create the branch if they really need it. They have these permissions to create branches via Gerrit GUI.

Let me know if we need to bring this matter up.

Thanks a ton
Jess

On Thu Dec 21 15:25:08 2017, Frank.Obrien@amdocs.com wrote:
> Gildas,
> Hi, The branches are in the body of the jira and posted to onap-
> discuss - we will need to discuss what to do with the duplicated and
> ones that don't require a branch yet.
> https://lists.onap.org/pipermail/onap-discuss/2017-
> December/007033.html
> Take all the highlighted green strings and retrofit them in the URL
> to see them Example
>
> aaf/authz
>
> is
> https://gerrit.onap.org/r/#/admin/projects/aaf/authz,branches
>
> Some correlation will need to be done to identify the teams for
> example optf = Homing
>
>
> ----------------------------------- https://lf-onap.atlassian.net/browse/INT-
> 373 extract
>
>
> Missing amsterdam because repo should be locked
>
> aai/aai-service - see https://lists.onap.org/pipermail/onap-
> discuss/2017-November/006191.html
>
> https://jira.onap.org/images/icons/emoticons/forbidden.png
> Capitalization (Amsterdam should be amsterdam)
>
> vnfrqts/requirements
>
> https://jira.onap.org/images/icons/emoticons/forbidden.png Missing
> both amsterdam and release-1.1.0 - only has master (some may move to
> Beijing-only which is OK)
>
> oom/registrator
>
> https://gerrit.onap.org/r/#/admin/projects/oom/registrator,branches
>
> ui
>
> aaf/authz
>
> aaf/cadi
>
> aaf/inno
>
> aaf/luaplugin
>
> ccsdk/dashboard
>
> ccsdk/storage/esaas
>
> ccsdk/platform/blueprints
>
> ccsdk/platform/plugins
>
> dcaegen2/analytics
>
> dcaegen2/collectors
>
> dcaegen2/collectors/snmptrap
>
> dcaegen2/platform
>
> dcaegen2/platform/registrator
>
> dmaap/buscontroller
>
> dmaap/dbcapi
>
> dmaap/datarouter
>
> doc/tools
>
> externalapi/nbi
>
> modeling/modelspec
>
> multicloud/azure
>
> optf/cmso
>
> optf/has
>
> optf/osdf
>
> policy/api
>
> policy/gui
>
> policy/pap
>
> policy/pdp
>
> sdnc/parent (deprecated?)
>
> university
>
> vnfrqts/epics
>
> vnfrqts/guidelines
>
> vnfrqts/testcases
>
> vnfrqts/usecases
>
> vnfsdk/compliance
>
> vnfsdk/functest
>
> vnfsdk/lctest
>
> (why amsterdam only in vnfsdk/model ?)
>
> vnfsdk/pkgtools
>
> vnfsdk/validation
>
>
>
> https://jira.onap.org/images/icons/emoticons/forbidden.png Missing
> amsterdam but has release-1.1.0 (should cherry pick to amsterdam and
> delete the release-1.1.0 branch)
>
> sdnc/adaptors
>
> sdnc/core
>
> sdnc/plugins
>
> ui/dmaapbc
>
>
>
> https://gerrit.onap.org/r/#/admin/projects/sdnc/adaptors,branches
>
> https://jira.onap.org/images/icons/emoticons/forbidden.png Ambiguous
> - has both release-1.1.0 and amsterdam - which is the active amsterdam
> branch
>
> Some like sdnc/northbound and oom have both (oom release-1.1.0 is
> being removed Friday) - thanks Borislav for reminding and de Talhouet,
> Alexis
> alexis.de_talhouet@bell.ca[https://jira.onap.org/images/icons/mail_sma
> ll.gif]<alexis.de_talhouet@bell.ca>
> for the quick-in-meeting fix/cherry-picks
>
> https://gerrit.onap.org/r/#/admin/projects/sdnc/northbound,branches
>
> https://gerrit.onap.org/r/#/admin/projects/oom,branches
>
> https://jira.onap.org/images/icons/emoticons/add.png no amsterdam
> branch - but likely because work is only in Beijing (master) - for
> some of these there is no container in OOM for example yet
>
> aai/babel
>
> aai/champ
>
> aai/gizmo
>
> sdnc/architecture
>
> sdnc/features
>
> vvp/ansible-ice-bootstrap
>
> vvp/cms
>
> vvp/devkit
>
> vvp/documentation
>
> vvp/engagementmgr
>
> vvp/gitlab
>
> vvp/image-scanner
>
> vvp/jenkins
>
> vvp/portal
>
> vvp/postgresql
>
> vvp/test-engine
>
> vvp/validation-scripts
>
>
>
>
> From: Gildas Lanilis gildas.lanilis@huawei.com
> Sent: Thursday, December 21, 2017 13:45
> To: helpdesk@onap.org; Michael O'Brien <Frank.Obrien@amdocs.com>
> Cc: Kenny Paul <kpaul@linuxfoundation.org>; Phil Robb
> <probb@linuxfoundation.org>
> Subject: Amsterdam Missing branches
>
> Hi Helpdesk,
>
> I am creating this ticket to follow up with an issue Michael brought
> up at TSC meeting this am.
> Looks like some repos have missing branches for Amsterdam. Michael has
> created defect https://lf-onap.atlassian.net/browse/INT-373
>
> Michael,
> Looking at Jira issue https://lf-onap.atlassian.net/browse/INT-373 I can't
> find the list of missing branches. Could you help out? That will help
> LF to move forward.
>
>
> Thanks,
> Gildas
>
> [HuaweiLogowithName]
> Gildas Lanilis
> ONAP Release Manager
> Santa Clara CA, USA
> gildas.lanilis@huawei.com<gildas.lanilis@huawei.com>
> Mobile: 1 415 238 6287
>
> 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>

Will discuss in Jan with Gildas and Jessica

.

.

.