Re: [release] SM projects status report

Guillaume Lambert

Hi all

Ariel,  I am back at the office since yesterday.
I've published our release plan details on jira today
I looked at Luis  last week email and we are in the process of performing the last steps to participate the release.
Martial did a big part of the job before I came back.  Build is OK and all our Junit and functional passed.
We have a problem with the procedure to publish on Nexus because we are using git submodules folders for our functests
and it appears the build release job use a 'git clone --submodule-recursive'
I am currently with the staff on IRC to try to fix the problem.

Hope this helps


De : Anton Ivanov [anton.ivanov@...]
Envoyé : mardi 4 septembre 2018 10:22
À : Ariel Adam; Luis Gomez; LAMBERT Guillaume IMT/OLN; OLLIVIER Cédric IMT/OLN; Scott Melton; Donald Hunter; An Ho
Cc : Release; <tsc@...>
Objet : Re: [release] SM projects status report

On 09/04/18 06:21, Ariel Adam wrote:
Hi everyone.
Relating to the list Luis provided and given that our time is short we'd appreciate if the following people could provide an updated status on their component and if and what is blocking them:
  • JSON-RPC - Anton
  • TransportPCE - Guillaume/Cedric
  • TSDR - Scott
  • Unimgr - Donald 
  • NEMO - An
  • USC - An
Obviously we should have planned better and provided the self managed projects more time however this is the first time we are implementing the new managed/unmanged project process and there is a learning curve.
In order for us to release on time (Thursday) and have the PR published on Friday morning (which is critical for the ODL project positioning) we need everything closed ASAP. 

If anyone noticed that one of the PTLs mentioned is no longer active please update us so we can find the relevant person.


On Mon, Sep 3, 2018 at 8:53 PM Luis Gomez <ecelgp@...> wrote:
Following projects are being tracked (at least someone responded to [0]):

1) SM projects participating in the common distribution, should go through the steps in [1] <- Please check updated info:
- Honeycomb: already released, misses dist sanity check (not critical).
- JSON-RPC: already released, misses add to distribution.

All done, patch to add to distribution submitted.

It is not green, but the error looks like coming from somewhere else:

[ERROR] Failed to execute goal on project opendaylight: Could not resolve dependencies for project org.opendaylight.integration:opendaylight:pom:0.10.0-SNAPSHOT: The following artifacts could not be resolved: org.opendaylight.honeycomb.vbd:vbd-features:xml:features:1.5.0-SNAPSHOT, org.opendaylight.tsdr:features-tsdr:xml:features:1.7.0-SNAPSHOT, org.opendaylight.unimgr:features4-unimgr:xml:features:0.5.0-SNAPSHOT: Could not find artifact org.opendaylight.honeycomb.vbd:vbd-features:xml:features:1.5.0-SNAPSHOT in opendaylight-snapshot (


- SNMP4SDN: already released, misses dist sanity check (not critical).
- SXP: already released.
- TransportPCE: misses creating the release.
- TSDR: misses stable/fluorine branch and creating release.
- Unimgr: already released, misses add to distribution.

2) SM projects not participating in the common distribution, they have to provide their own distribution and install instructions:

- NEMO: misses creating the release.
- USC: misses creating the release.


release mailing list


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.

Join to automatically receive all group messages.