Re: [release] [OpenDaylight TSC] Sodium code freeze
All of the CSIT results have been marked OKAY or IGNORE. I think we can
move forward with the SR4 release now.
The three jobs that I had marked as blocker (2 netconf and 1 controller)
was so that I could have time to investigate if the failures were due to
a regression or not. I spent some cycles with the jobs in the sandbox and
it is clear the jobs are just unstable and fail periodically. The failure rate
is the same for SR3 vs SR4 in all cases.
tracking sheet is here:
On 8/13/20 10:27 AM, Daniel de la Rosa wrote:
As we agree on today's TSC, we are going to wait for this LFN IT ticket IT-20355to be resolved before we can move forward with any other release, including Sodium SR4 and Aluminum
On Tue, Aug 11, 2020 at 10:56 AM <srinivas.rachakonda@...> wrote:
I have updated the spreadsheet for Netvirt and Genius.
From: TSC@... <TSC@...> On Behalf Of Daniel de la Rosa
Sent: 11 August 2020 11:42
To: <tsc@...> <tsc@...>
Cc: Release <release@...>
Subject: Re: [OpenDaylight TSC] Sodium code freeze
Stable/sodium has been locked so we can move forward with picking up the Sodium SR4 RC. I have picked up 462/int 602 and as you can see we have significant number of issues
Please proceed to review Sodium SR4 AR 462 and let us know if these are blockers
On Fri, Jul 31, 2020 at 7:02 PM Daniel de la Rosa via lists.opendaylight.org <ddelarosa=luminanetworks.com@...> wrote:
Hello TSC and all
We are going to code freeze Sodium for all Managed Projects ( cut and lock release branches ) on Monday August 7th 2020 at 10 am pst.
Please remember that we only allow blocker bug fixes in release branch after code freezes
ps. Release schedule and checklist for any feedback