[opensuse-project] Confirming list of stakeholders for the openSUSE Leap 15.2.1 mini interlock on 19th October
Hello openSUSE! I'd like to confirm with a community on the list of stakeholders to sign off under the openSUSE Leap 15.2.1 go/nogo on a currently proposed release day of 4th November. The signoff (mini-interlock) should happen on Monday 19th Oct (intentionally after the openSUSE and LibreOffice conference). The exact time will be determined based on the geolocation of the audience. The signoff will happen on a jitsi meeting and progress-o-o and we will share the report on wiki and mailing lists. Currently proposed list of stakeholders is the regular crew of CtLG weekly updates (List can be found at last meeting minutes) and DimStar. https://etherpad.opensuse.org/p/ClosingTheLeapGap-meeting) What exactly are we signing off: agreed items listed at https://etherpad.opensuse.org/p/ClosingTheLeapGap-20200924-interlock-discuss... https://en.opensuse.org/openSUSE:Roadmap in case of nogo we'd simply start to work on openSUSE Leap 15.3 release right away without an intermediate Leap 15.2.1 release. Please reach out to me if you believe you should be part of the sign- off itself. Thank you and Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer N�����r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7���0�����Ǩ�
Hello, Am Dienstag, 13. Oktober 2020, 11:27:22 CEST schrieb Lubos Kocman:
What exactly are we signing off: agreed items listed at https://etherpad.opensuse.org/p/ClosingTheLeapGap-20200924-interlock-discuss...
Looks mostly good, with one exception: Migration of Leap 15.2 to Leap 15.2.1. Not necessarily the older releases. Our docs say you need to migrate from release to release and follow the n+1 migration scenario (do not skip any release in between). I know that 15.2.1 is technically a separate release, but for users it will probably look like a "respin of 15.2 including all maintenance updates". Of course there are changes "under the hood" (like using the SLE binary RPMs), but that's not too user-visible or -relevant. Therefore I'd like to see official support for updates from 15.1 to 15.2.1 (skipping 15.2) and also (next year) from 15.2 to 15.3 (skipping 15.2.1). On the positive side, our upgrades rarely break, so hopefully this request will only mean a bit of paperwork ;-) Regards, Christian Boltz --
[Factory] is also expected to have new features and behaviours, which will surprise people, Oooow, I like surprises - as long as they frighten the crap out of me and make me soil my panties :-) . [> Carlos E. R. and Basil Chupin in opensuse-factory] -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Hello Christian, that's a fair point. And I agree that Leap 15.2.1 would be basically respin of 15.2 + Updates with more SUSE LLC signed binaries. We do run tests for releases up to 42.3 however our main focus is on 15.2 -> 15.2.1. Lubos On Wed, 2020-10-14 at 17:42 +0200, Christian Boltz wrote:
Hello,
Am Dienstag, 13. Oktober 2020, 11:27:22 CEST schrieb Lubos Kocman:
What exactly are we signing off: agreed items listed at https://etherpad.opensuse.org/p/ClosingTheLeapGap-20200924-interlock-discuss...
Looks mostly good, with one exception:
Migration of Leap 15.2 to Leap 15.2.1. Not necessarily the older releases. Our docs say you need to migrate from release to release and follow the n+1 migration scenario (do not skip any release in between).
I know that 15.2.1 is technically a separate release, but for users it will probably look like a "respin of 15.2 including all maintenance updates". Of course there are changes "under the hood" (like using the SLE binary RPMs), but that's not too user-visible or -relevant.
Therefore I'd like to see official support for updates from 15.1 to 15.2.1 (skipping 15.2) and also (next year) from 15.2 to 15.3 (skipping 15.2.1).
On the positive side, our upgrades rarely break, so hopefully this request will only mean a bit of paperwork ;-)
Regards,
Christian Boltz --
[Factory] is also expected to have new features and behaviours, which will surprise people, Oooow, I like surprises - as long as they frighten the crap out of me and make me soil my panties :-) . [> Carlos E. R. and Basil Chupin in opensuse-factory] --
Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer N�����r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7���0�����Ǩ�
The date has changed from 19th October to 20th October due to unavailablity of some of the stakeholders. This particular document will be used for the signoff. https://en.opensuse.org/Portal:Jump/Leap15.2.1:GoNogo On Thu, 2020-10-15 at 11:25 +0200, Lubos Kocman wrote:
Hello Christian,
that's a fair point. And I agree that Leap 15.2.1 would be basically respin of 15.2 + Updates with more SUSE LLC signed binaries.
We do run tests for releases up to 42.3 however our main focus is on 15.2 -> 15.2.1.
Lubos
On Wed, 2020-10-14 at 17:42 +0200, Christian Boltz wrote:
Hello,
Am Dienstag, 13. Oktober 2020, 11:27:22 CEST schrieb Lubos Kocman:
What exactly are we signing off: agreed items listed at https://etherpad.opensuse.org/p/ClosingTheLeapGap-20200924-interlock-discuss...
Looks mostly good, with one exception:
Migration of Leap 15.2 to Leap 15.2.1. Not necessarily the older releases. Our docs say you need to migrate from release to release and follow the n+1 migration scenario (do not skip any release in between).
I know that 15.2.1 is technically a separate release, but for users it will probably look like a "respin of 15.2 including all maintenance updates". Of course there are changes "under the hood" (like using the SLE binary RPMs), but that's not too user-visible or -relevant.
Therefore I'd like to see official support for updates from 15.1 to 15.2.1 (skipping 15.2) and also (next year) from 15.2 to 15.3 (skipping 15.2.1).
On the positive side, our upgrades rarely break, so hopefully this request will only mean a bit of paperwork ;-)
Regards,
Christian Boltz --
[Factory] is also expected to have new features and behaviours, which will surprise people, Oooow, I like surprises - as long as they frighten the crap out of me and make me soil my panties :-) . [> Carlos E. R. and Basil Chupin in opensuse-factory] -- Best regards
Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
On Thu 2020-10-15, Lubos Kocman wrote:
Therefore I'd like to see official support for updates from 15.1 to 15.2.1 (skipping 15.2) and also (next year) from 15.2 to 15.3 (skipping 15.2.1). that's a fair point. And I agree that Leap 15.2.1 would be basically respin of 15.2 + Updates with more SUSE LLC signed binaries.
We do run tests for releases up to 42.3 however our main focus is on 15.2 -> 15.2.1.
I believe it'd be great to see the lifecycles of the different openSUSE (Leap) releases summarized, first as they are as of today, and second as they'd look like assuming Jump/15.2.1 sees agreement in the sign off you are driving. (Feel free to ping me if you'd like to discuss/understand what I mean in case I'm not clear. ;-) Thanks, Gerald -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (3)
-
Christian Boltz -
Gerald Pfeifer -
Lubos Kocman