2022.09 Chlorine MRI status


Robert Varga
 

Hello everyone,

Since we are well in the 2022.09 Simultaneous Release (Chlorine), here is a quick summary of where we are at:

- MRI projects up to and including AAA have released
- MSI projects have preliminary patches staged at https://git.opendaylight.org/gerrit/q/topic:chlorine-mri
- NETCONF is awaiting a bug scrub and the corresponding release. There are quite a few issues to scrub and we also need some amount of code reorg withing the repo, which in itself may entail breaking changes. There are quite a few unreviewed patches pendign as well. Given the raging summer in the northern hemosphere, I expect netconf-4.0.0 release to happen in about 2-3 weeks' time (i.e. last week of July 2022)
- BGPCEP has a few deliverables yet to be finished and the corresponding 0.18.0 release being dependent on NETCONF, my working assumption is having the release available mid-August 2022

As such, everyone running Java should have Java 17 as their default environment. Not only is it cool as $EXPLENTIVE, but it is becoming a requirement very soon. 2022.03 Sulfur is handling it just fine (as far as I know) and you cannot interact with 2022.09 Chlorine without it.

Daniel: is the Chlorine scheduled approved? My (inprefect) tracking says it is yet to be voted on.

Regards,
Robert

P.S.: my default JDK is Java 17 and I am encountering zero issues with it on either 2022.09 or 2022.03 release streams. Please switch to Java 17 if you can and report any issues you encounter.


Daniel de la Rosa
 




On Wed, Jul 6, 2022 at 4:35 PM Robert Varga <nite@...> wrote:
Hello everyone,

Since we are well in the 2022.09 Simultaneous Release (Chlorine), here
is a quick summary of where we are at:

- MRI projects up to and including AAA have released
- MSI projects have preliminary patches staged at
https://git.opendaylight.org/gerrit/q/topic:chlorine-mri
- NETCONF is awaiting a bug scrub and the corresponding release. There
are quite a few issues to scrub and we also need some amount of code
reorg withing the repo, which in itself may entail breaking changes.
There are quite a few unreviewed patches pendign as well. Given the
raging summer in the northern hemosphere, I expect netconf-4.0.0 release
to happen in about 2-3 weeks' time (i.e. last week of July 2022)
- BGPCEP has a few deliverables yet to be finished and the corresponding
0.18.0 release being dependent on NETCONF, my working assumption is
having the release available mid-August 2022

As such, everyone running Java should have Java 17 as their default
environment. Not only is it cool as $EXPLENTIVE, but it is becoming a
requirement very soon. 2022.03 Sulfur is handling it just fine (as far
as I know) and you cannot interact with 2022.09 Chlorine without it.

Daniel: is the Chlorine scheduled approved? My (inprefect) tracking says
it is yet to be voted on.

Well I got your approval 


but I can put out for vote and hopefully get it approved on next TSC meeting 



 

Regards,
Robert

P.S.: my default JDK is Java 17 and I am encountering zero issues with
it on either 2022.09 or 2022.03 release streams. Please switch to Java
17 if you can and report any issues you encounter.