+1 Thanh

+1 Thanh

Hi Wang, You need to run your maven-staging job https://jenkins.opendaylight.org/releng/view/telemetry/job/telemetry-maven-stage-neon/ once it passes you will need to work with helpdesk to release the

+1 Thanh

+1 Thanh

+1 Thanh

Hi Luis, It's not permanent. It's only active when needed to prevent people from accidentally utilizing the powers during times it is not needed. So those who have the super powers should be careful u

Almost. You will always have +2 voting rights on the projects where you are committer. "Locking" the branch just means we disable Submit for all projects. The releng super user group will then get tem

Hi Anil, Can you copy the validation error messages so that we can look at them? Thanks, Thanh

Hi Helpdesk, Please disable the supercommitter powers. The mdsal-4.0.1 version bump is complete. Thanks, Thanh

NetVirt: https://github.com/opendaylight/netvirt/blob/master/karaf/pom.xml#L120-L127 Is the karaf artifact expected to be deployed? there is a comment that says "temporarily" which makes me think we'r

I don't think we should keep branch locked after the managed release is out the door. The remaining projects are self-managed projects which can release anytime they want. Regards, Thanh

Option 1 Thanh

Hello TSC, Daniel De La Rosa (cc'd) will be my proxy next week for the TSC meeting on June 13th 2019. Regards, Thanh

+1 Thanh

+1 for Option 2 (Jointly with ONAP/OPNFV) Regards, Thanh

Hi Anil, For obvious reasons I can no longer see Maven Central configuration for ODL. What must we do to ensure that we can get Maven Central releases moving forward? I took at look at https://oss.son

I think only LF can see issues opened with Sonatype because they tie issues to customer accounts and do not allow anonymous access. Regards, Thanh

Agreed. We could have the to-central jobs be only run when we decide to release so that we don't pre-maturely stage them in central. This would require injecting a step in our release process where to

+1 Thanh