Date
1 - 3 of 3
releasing Sodium SR2
JamO Luhrsen
Hi folks,
I think we should already be well under way of the process to release
Sodium SR2 right? Unless I missed some agreement to push it, it's
scheduled [0] for release this thursday 1/30/2020.
I don't see any blocker bugs in jira.
I do see quite a few patches open for sodium [1], but we still have SR3
planned at the end of May for them to make it. A big chunk of those
patches are close to 2 months old, so maybe not important any more.
Another chunk are new as of today for transportpce, so probably not
even intended to make SR2.
I propose we pick a release candidate from the most recent autorelease
build [2], and vet the CSIT results [3] using that build. With a little
luck and work, we may be able to release on time, as the number of jobs
with failures are the same as SR1 and maybe the failures will be quick
to nail down as NOT regressions.
Can we move forward on this and try to meet our schedule?
Thanks,
JamO
[0] https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
[1] https://git.opendaylight.org/gerrit/q/branch:stable/sodium+status:open
[2] https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/326/
[3] https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=2145734982
I think we should already be well under way of the process to release
Sodium SR2 right? Unless I missed some agreement to push it, it's
scheduled [0] for release this thursday 1/30/2020.
I don't see any blocker bugs in jira.
I do see quite a few patches open for sodium [1], but we still have SR3
planned at the end of May for them to make it. A big chunk of those
patches are close to 2 months old, so maybe not important any more.
Another chunk are new as of today for transportpce, so probably not
even intended to make SR2.
I propose we pick a release candidate from the most recent autorelease
build [2], and vet the CSIT results [3] using that build. With a little
luck and work, we may be able to release on time, as the number of jobs
with failures are the same as SR1 and maybe the failures will be quick
to nail down as NOT regressions.
Can we move forward on this and try to meet our schedule?
Thanks,
JamO
[0] https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
[1] https://git.opendaylight.org/gerrit/q/branch:stable/sodium+status:open
[2] https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/326/
[3] https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=2145734982
Thanks Jamo. .We have agreed on the last TSC meeting to pick the last Sodium AR J8 as RC... @Anil Belur are you working on that?
On Tue, Jan 28, 2020 at 10:26 AM JamO Luhrsen <jluhrsen@...> wrote:
Hi folks,
I think we should already be well under way of the process to release
Sodium SR2 right? Unless I missed some agreement to push it, it's
scheduled [0] for release this thursday 1/30/2020.
I don't see any blocker bugs in jira.
I do see quite a few patches open for sodium [1], but we still have SR3
planned at the end of May for them to make it. A big chunk of those
patches are close to 2 months old, so maybe not important any more.
Another chunk are new as of today for transportpce, so probably not
even intended to make SR2.
I propose we pick a release candidate from the most recent autorelease
build [2], and vet the CSIT results [3] using that build. With a little
luck and work, we may be able to release on time, as the number of jobs
with failures are the same as SR1 and maybe the failures will be quick
to nail down as NOT regressions.
Can we move forward on this and try to meet our schedule?
Thanks,
JamO
[0] https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
[1] https://git.opendaylight.org/gerrit/q/branch:stable/sodium+status:open
[2]
https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/326/
[3]
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=2145734982
--
JamO Luhrsen
That's what I gave in [3]
JamO
toggle quoted message
Show quoted text
JamO
On 1/28/20 10:39 AM, Daniel De La Rosa
wrote:
Thanks Jamo. .We have agreed on the last TSC meeting to pick the last Sodium AR J8 as RC... @Anil Belur are you working on that?
On Tue, Jan 28, 2020 at 10:26 AM JamO Luhrsen <jluhrsen@...> wrote:
Hi folks,
I think we should already be well under way of the process to release
Sodium SR2 right? Unless I missed some agreement to push it, it's
scheduled [0] for release this thursday 1/30/2020.
I don't see any blocker bugs in jira.
I do see quite a few patches open for sodium [1], but we still have SR3
planned at the end of May for them to make it. A big chunk of those
patches are close to 2 months old, so maybe not important any more.
Another chunk are new as of today for transportpce, so probably not
even intended to make SR2.
I propose we pick a release candidate from the most recent autorelease
build [2], and vet the CSIT results [3] using that build. With a little
luck and work, we may be able to release on time, as the number of jobs
with failures are the same as SR1 and maybe the failures will be quick
to nail down as NOT regressions.
Can we move forward on this and try to meet our schedule?
Thanks,
JamO
[0] https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
[1] https://git.opendaylight.org/gerrit/q/branch:stable/sodium+status:open
[2]
https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-sodium-mvn35-openjdk8/326/
[3]
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=2145734982
--