Re: [release] Sulfur code freeze
On 15/04/2022 02:23, Daniel de la Rosa wrote:
Anyhow, Integration test for AR#15 still has some issuesSo 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 ~4 hours and test results from that in another ~3 hours.
Based on the results of https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/219/, the release is GO from my perspective.
There seem to be OFP issues, though, I think Sangwook has the final say.
On the BGPCEP side of things, we have two failures:
1. one of them is a BGP policy 409, which I need to investigate, but I do not believe it's anything major
2. BGP ingest is plagued by https://jira.opendaylight.org/browse/CONTROLLER-2043, but I honestly think this is an environment issue
At any rate, looking at the schedule, we are *way* past the release date and in fact should be releasing Sulfur SR1 on 4/28, i.e. in two days.
I think we should just release as is, get the marketing stuff out, etc. and circle back for SR1 -- say, in two weeks. That would give us a few days of breathing time (I know I need some) and see what's what.
We also are ~2 weeks past the Chlorine MRI bump, so that switching gears makes a ton of sense -- I really want Chlorine to get us back on track with the calendar :)