Hello team Another friendly reminder to complete the content for all the Neon Jira tickets. Here is the link and what's required ODL Jira dashboard For each of the managed projects there should be JIR

i recently got the permissions to do so, so i just marked fluorine as released.. I'll do it for Neon when it releases Thanks

i did Fluorine SR1, 2 and 3 but it didnt let me do fluorine because of this reopened issue https://jira.opendaylight.org/projects/TSC/versions/10561 https://jira.opendaylight.org/browse/TSC-74 @Anil V

we should talk about the release dates and number of releases because it doesnt look like we are gonna have neon SR1 by tomorrow

This is the main topic we would like to review: the new release schedule proposal (thanks Luis) ... Event Fluorine Neon Sodium Release 2018-09-07 (+0 moths) 2019-03-25 (+0 months) 2019-09-05 (+0 month

Hello Abhijit As part of the release topic, we need to talk about Fluorine SR3 Thanks

Great, thanks for the update.

Robert It seems that this regression still happening so Luis is going to raise a ticket to get this fixed and be able to release Fluorine SR3... Any updates from your end? Thanks

Since this is fixed now and the other two blockers are not real blockers for fluorine sr3, https://jira.opendaylight.org/browse/AAA-185 https://jira.opendaylight.org/browse/BGPCEP-873 The spreadsheet

Ok we can pick 143 which is the next AR build to make sure that all the fixes are merged and vote tomorrow... thanks

Hi Robert... Agree on having this discussion this week but i have adjusted Sodium middle checkpoint for 7/4/19. Here is the current schedule https://docs.opendaylight.org/en/latest/release-process/rel

I'm not sure that we will have enough quorum on tomorrow's TSC meeting but we could definitely release SR3 as it is since customers are waiting.. Do we want to just move forward via email?

Luis. See the email below from Jamo regarding flourine sr4. I don’t think it is worth it at this time but we can review it in detail on the next tsc

Robert and Abhijit. Let's discuss this on the next TSC meeting so we can get approval from the whole team. This is a big change that in my opinion, shouldnt be happening in a service release. Thanks

Hello Robert It looks like we can move forward with Sodium code freeze but please confirm Thanks

Thanks Robert for pointing that out. Neon SR2 was originally scheduled for 8/8 but as suggested by Abhijit, we should release it since Transport PCE is self managed. We just need to for all projects t

Ok Robert, we can review this on tomorrow’s tsc meeting

Yes, that is correct. 09/05/2019 is still the sodium formal planned release Thanks

Hello ODL project leaders. Another friendly reminder to start working on your respective release notes for Sodium. Please let us know if you have any questions or concerns. https://docs.opendaylight.o

Luis, Robert and all So based on what we have today... for example, this neon release note https://docs.opendaylight.org/en/stable-neon/release-notes/projects/netconf.html we have : Major features Doc