Hello TSC Please approve Sulfur AR #30 as RC for Sulfur GA as soon as possible https://wiki.opendaylight.org/display/ODL/Sulfur+Formal+Release+Approval Thanks -- Daniel de la Rosa ODL Release Manager

ok @Ha, Sangwook and all TSC, if you are ok with releasing Sulfur in its current state, AR#30 and integration #220, please approve it at

Hey everyone, especially those working on ODL We are currently transitioning to JDK17 as part of Chlorine MRI bump. Unfortunately we are at this point 11 days past the deadline, so things are moving

So we have latest AR here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/ Triggered by Sangwook, because the previous run failed. We can expect AR #30 in

[snip] The old implementation is no longer present in netconf/master, hence this item is slated for delivery in 2022.09 Chlorine. Regards, Robert

Hello again, [snip] These issues have been addressed. Both these items are delivered, all projects participating on Sulfur GA verify each patch with both JDK11 and JDK17. This is now slated for

Hmm, that would be a major problem and really soon. Sigul is part of stage jobs -- stage i.e. build + sign. We are exactly 2 patches away from odlparent/master requiring JDK17 to build -- and that

+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes. Sigul (artifact

+1 Od: release@... <release@...> v mene používateľa Luis Gomez <ecelgp@...> Odoslané: piatok, 22. apríla 2022 1:57:03 Komu: Robert Varga Kópia: infrastructure@...; release@...;

LGTM, any change for updating current infra is +1 for me :)

Hello all, The version bump is complete, the master branch is promoted to the next release (Chlorine) and the "stable/sulfur" branch has been created. Note: The master branch (Chlorine) is unlocked

Hello all, The master branch is locked for Sulfur code freeze and branch cutting ("stable/sulfur") and master branch will be promoted to next (Chlorine), which will be the development version. Once

Hello everyone, we are currently defaulting to centos7-builder-4c-4g here: https://github.com/opendaylight/releng-builder/blob/master/jjb/defaults.yaml#L19= CentOS7 is ancient and cannot support our

Hello As discussed today, I won’t be able to attend next TSC meeting. If needed, Cédric can be my proxy. Kind Regards Guillaume Orange

Yes Anil is out this week so maybe @Andrew Grimberg can get somebody else to help with https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826 Anyhow, Integration test for AR#15

OK, then maybe it will help some marketing and/or white paper if anyone knows about these use cases in more detail :) Fair enough, I did not explained well myself, Java nano-service is still required

Just to qualify this end-to-end in terms of the NETCONF/RESTCONF pass-through case. netconf-maven-stage-master should produce a container containing the use-case, using whatever runtime (dynamic

Strictly speaking: we already do, but through external integrations and those bring very little in terms of engagement/contributions :( Weeeeeeeeeell. I could *very easily* sell you OSGi as: - the

So we still do not have that ticket taken care of, but I realized we can work it around by changing the builders -- which we did and I spent today releasing MRI projects, which are now integrated. I

Hello Luis Thanks for this feedback. I mostly share your concerns here at least about 2 and 3. (about 1, I am not very involved in cloud use-cases and the situation is a bit different in core