From hui.zhi.zhao at suse.com  Fri Feb  2 22:13:15 2024
From: hui.zhi.zhao at suse.com (Hui-Zhi Zhao)
Date: Sat, 3 Feb 2024 06:13:15 +0800
Subject: Fwd: SUSE / Lenovo Technical Review Meeting (TRF)
References: <KL1PR03MB7904926941B65B4528304658B7432@KL1PR03MB7904.apcprd03.prod.outlook.com>
Message-ID: <37A4B5C3-B34B-49C9-9141-CF9762C2588F@suse.com>

Hello everyone,

The meeting invitation of Lenovo TRF has been sent out, it will be held online via Teams. Feel free to join the meeting and let me know if you have any questions.

?
Regards,
Hui-Zhi

> Begin forwarded message:
> 
> From: Chris McDermott2 <lmcdermott at lenovo.com>
> Subject: SUSE / Lenovo Technical Review Meeting (TRF)
> Date: February 1, 2024 at 09:45:34 GMT+8
> To: Michal Svec <msvec at suse.com>, Daniel Rahn <drahn at suse.com>, Sergio Oc?n <sergio.ocon at suse.com>, Knut Trepte <knut.trepte at suse.com>, Andreas Jaeger <aj at suse.com>, Tim Irnich <tim.irnich at suse.com>, Joachim Werner <joe at suse.com>, Will Godfrey <Will.Godfrey at suse.com>, Fran?ois-Xavier Houard <francois-xavier.houard at suse.com>, Hui Zhi Zhao <hui.zhi.zhao at suse.com>
> Cc: Drew Jackman <djackman at suse.com>, Adam Deng1 Deng <dengdeng1 at lenovo.com>, Adrian Huang12 <ahuang12 at lenovo.com>, Xiaochun XC17 Li <lixc17 at lenovo.com>, Kelvin Shieh <kshieh at lenovo.com>, Tzu ting Yu1 <tyu1 at lenovo.com>, Ajay Dholakia <adholakia at lenovo.com>, Makoto Ono <mono2 at lenovo.com>, Russell Resnick <rresnick at lenovo.com>, Warren Bailey1 <wbailey1 at lenovo.com>, Wilson Velez <wvelez at lenovo.com>, David Cosby <dcosby at lenovo.com>, Fred Bower <fbower at lenovo.com>, Patrick Caporale <pcaporale at lenovo.com>, Jeffery Van Heuklon <jvanh at lenovo.com>, Ana Irimiea <airimiea at lenovo.com>, Jay Bryant1 <jbryant1 at lenovo.com>, Jean-Marius Antonica <jantonica at lenovo.com>, Billzheng Sun1 <zsun1 at lenovo.com>, Bobby Parson <bparson at lenovo.com>, Eric YS Li <eli4 at lenovo.com>, Gary Cudak <gcudak at lenovo.com>, Tim Tennant <ttennant at lenovo.com>, Shawn Austvold <saustvold at lenovo.com>, Ileana Petrisor <ipetrisor at lenovo.com>, Michael He ZhiGeng <hezg1 at lenovo.com>
> 
> Agenda
> All sessions are under NDA.
> The meetings will be recorded.
> The presentations will be made available to the participants after the meetings.
>  
> Sessions:
> SUSE Linux Enterprise Products / Lenovo Hardware portfolio & roadmap (12/March)
> Lenovo SAP / SUSE SAP ( 13/March)
> Security in SLES / Lenovo DataCenter / Lenovo LiCO (AI and HPC)  (13/March)
> Edge, Lenovo Cloud, Rancher and SLE BCI (14/March)
>  
>  
> Session: SUSE Linux Enterprise Products / Lenovo Hardware portfolio & roadmap
> Date: 12/Mar/2024
> Topic
> Company
> Presenter
> CET, Europe (UTC+1)
> EDT, US (UTC-4)
> MDT, US (UTC-6)
> PDT, US (UTC-7)
> CST, China (UTC+8)
> 14:00 - 14:30
> 09:00 - 09:30
> 07:00 - 07:30
> 06:00 - 06:30
> 21:00 - 21:30
> SUSE Linux Enterprise Roadmap
> SUSE
> Michal Svec
> 14:30 ? 15:30
> 09:30 ? 10:30
> 07:30 ? 08:30
> 06:30 ? 07:30
> 21:30 ? 22:30
> SLE Micro/SUSE ALP
> SUSE
> Daniel Rahn / Sergio Oc?n
> 15:30 - 16:30
> 10:30 - 11:30
> 08:30 - 09:30
> 07:30 - 08:30
> 22:30 - 23:30
> Lenovo HW Roadmaps - Servers
> Lenovo
> Russell Resnick or Mark Bica
> Warren Bailey
> Wilson Velez
> David Cosby
> Topics / Objectives
>  
> 
> Session: Security in SLES / Lenovo DataCenter / Lenovo LiCO (AI and HPC)
>  
> Date: 13/Mar/2024
> Topic
> Company
> Presenter
>  
> CET, Europe (UTC+1)
> EDT, US (UTC-4)
> MDT, US (UTC-6)
> PDT, US (UTC-7)
> CST, China (UTC+8)
>  
> 14:00 ? 14:30
> 09:00 - 09:30
> 07:00 - 07:30
> 06:00 - 06:30
> 21:00 - 21:30
> Security in SLES
> SUSE
> Knut Trepte
>  
> 14:30 ? 15:30
> 09:30 ? 10:30
> 07:30 ? 08:30
> 06:30 ? 07:30
> 21:30 ? 22:30
> Lenovo DataCenter HW Technology Trends / Management Software
> Lenovo
> Patrick Caporale / Fred Bower
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 15:30 - 16:00
> 10:30 - 11:00
> 08:30 - 09:00
> 07:30 - 08:00
> 22:30 - 23:00
> Lenovo LiCO (AI and HPC)
> Lenovo 
> Ana Irimiea
>  
> 16:00 ? 16:30
> 11:00-11:30
> 09:00-09:30
> 08:00 ? 08:30
> 23:00 ? 23:30
> Lenovo SAP
> Lenovo
>  
>  
> 16:30 ? 17:00
> 11:30 ? 12:00
> 09:30 ? 10:00
> 08:30 ? 09:00
> 23:00 ? 00:00
> SUSE SAP
> SUSE
> Andreas Jaeger
>  
> Topics / Objectives
>  
>  
>  
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Session: Edge, Lenovo Cloud, Rancher and SLE BCI
>  
> Date: 14/Mar/2024
> Topic
> Company
> Presenter
>  
> CET, Europe (UTC+1)
> EDT, US (UTC-4)
> MDT, US (UTC-6)
> PDT, US (UTC-7)
> CST, China (UTC+8)
>  
> 14:00 - 14:40
> 09:00 - 09:40
> 07:00 - 07:40
> 06:00 - 06:40
> 21:00 - 21:40
> Lenovo Edge
> Lenovo
> Benoit Robert
> Bill Zheng
>  
> 14:40 ? 15:30
> 09:40 ? 10:30
> 07:40 ? 08:30
> 06:40 ? 07:30
> 21:40 ? 22:30
> SUSE Edge
> SUSE
> Andrew Gracey
> Tim Irnich
> Joachim Werner
>  
> 15:30 - 16:00
> 10:30 - 11:00
> 08:30 - 09:00
> 07:30 - 08:00
> 22:30 - 23:00
> Rancher Products Overview and Roadmap
> SUSE
> Will Godfrey
>  
> 16:00 - 16:30
> 11:00 - 11:30
> 09:00 - 09:30
> 08:00 - 08:30
> 23:00 - 23:30
> Lenovo Clould&LOC-A
> Lenovo
> Jean-Marius Antonica
> Jay S. Bryant
>  
> 16:30 ? 17:00
> 11:30 ? 12:00
> 09:30 ? 10:00
> 08:30 ? 09:00
> 23:30 ? 00:00
> SLE BCI
> SUSE
> Fran?ois-Xavier Houard
>  
> Topics / Objectives
>  
> Retail/Manufacturing, Progress update on Telcom.
>  
>  
> 
>  
> ________________________________________________________________________________
> Microsoft Teams meeting
> Join on your computer, mobile app or room device
> Click here to join the meeting <https://teams.microsoft.com/l/meetup-join/19%3ameeting_MDkxMDMxNzQtNDIwMy00YThjLTg3NmEtZjAwMjJjMjQ0MTVl%40thread.v2/0?context=%7b%22Tid%22%3a%225c7d0b28-bdf8-410c-aa93-4df372b16203%22%2c%22Oid%22%3a%2201d3a423-5cb2-4c9c-a32f-d19bd20dfcc2%22%7d>
> Meeting ID: 428 458 013 841
> Passcode: hfWssT
> Download Teams <https://www.microsoft.com/en-us/microsoft-teams/download-app> | Join on the web <https://www.microsoft.com/microsoft-teams/join-a-meeting>
> Or call in (audio only)
> +1 347-941-1612,,687646204# <tel:+13479411612,,687646204#>   United States, New York City
> Phone Conference ID: 687 646 204#
> Find a local number <https://dialin.teams.microsoft.com/e95cb7ca-86ab-4954-a7bd-2e18db5104ed?id=687646204> | Reset PIN <https://dialin.teams.microsoft.com/usp/pstnconferencing>
> Learn More <https://aka.ms/JoinTeamsMeeting> | Meeting options <https://teams.microsoft.com/meetingOptions/?organizerId=01d3a423-5cb2-4c9c-a32f-d19bd20dfcc2&tenantId=5c7d0b28-bdf8-410c-aa93-4df372b16203&threadId=19_meeting_MDkxMDMxNzQtNDIwMy00YThjLTg3NmEtZjAwMjJjMjQ0MTVl at thread.v2&messageId=0&language=en-US>
> ________________________________________________________________________________
>  
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240203/995b72bb/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mail Attachment.ics
Type: text/calendar
Size: 11319 bytes
Desc: not available
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240203/995b72bb/attachment-0001.ics>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240203/995b72bb/attachment-0003.htm>

From rtsvetkov at suse.com  Thu Feb  8 14:23:21 2024
From: rtsvetkov at suse.com (Radoslav Tsvetkov)
Date: Thu, 8 Feb 2024 15:23:21 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change Acceptance
Message-ID: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>

Dear SLE Stakeholders,

This serves as a reminder regarding the upcoming deadline for final
acceptance of features and changes for SLE Products. To ensure a smooth
development process and product release on schedule, we're aiming for
finalization by 2024-03-19.

Key information:

   - Feature and Change Acceptance Deadline also kABI soft freeze:
   *2024-02-29*
   - Bug Fix Submissions: We will continue to accept bug fixes after this
   deadline, with focus on P1 and P2 severity levels.
   - Change Acceptance After Deadline: Due to potential schedule risks, any
   feature or feature requests submitted after  *2024-02-29* will
require *explicit
   approval by the Product **CCB *(Change Control Board).
   - Hard kABI Freeze: Please note that we will have a hard kABI freeze on
   2024-03-19. This means, after this date, changes to the application
   binary interface will no longer be permitted.

What's next?

   - Please review all outstanding feature and change requests and finalize
   your decisions by  *2024-02-21*.
   - If you have any questions or require clarification on specific
   items, please don't hesitate to reach out to the product team.
   - Submit any remaining P1 and P2 bug fixes following the established
   process.

By adhering to these deadlines, we can maintain a clear development path
and deliver a high-quality product on time. Your timely cooperation is
greatly appreciated.

Thank you for your continued support of SUSE Linux Enterprise.

Sincerely,

-- 
*Radoslav Tsvetkov*
Senior Program Manager SUSE BCL Linux
<https://www.suse.com/solutions/business-critical-linux/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240208/f66ced8f/attachment.htm>

From matthias.bgg at gmail.com  Fri Feb  9 16:49:19 2024
From: matthias.bgg at gmail.com (Matthias Brugger)
Date: Fri, 9 Feb 2024 16:49:19 +0000
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
Message-ID: <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>

Hi Radoslav,

I think it would make sense to provide this information to the wider 
developer audience (e.g. devel at suse.de), so that everybody is on the 
same page about the kABI freezes.

Regards,
Matthias

On 2/8/24 14:23, Radoslav Tsvetkov wrote:
> Dear SLE Stakeholders,
> 
> This serves as a reminder regarding the upcoming deadline for final 
> acceptance of features and changes for SLE Products. To ensure a smooth 
> development process and product release on schedule, we're aiming for 
> finalization by 2024-03-19.
> 
> Key information:
> 
>   * Feature and Change Acceptance Deadline also kABI soft
>     freeze:*2024-02-29*
>   * Bug Fix Submissions:?We will continue to accept bug fixes after this
>     deadline,?with focus on P1 and P2 severity levels.
>   * Change Acceptance After Deadline:?Due to potential schedule
>     risks,?any feature or feature requests submitted after
>     *2024-02-29*?will require *explicit approval by the Product **CCB
>     *(Change Control Board).
>   * Hard kABI Freeze:?Please note that we will have a hard kABI freeze
>     on 2024-03-19.?This means,?after this date,?changes to the
>     application binary interface will no longer be permitted.
> 
> What's next?
> 
>   * Please review all outstanding feature and change requests and
>     finalize your decisions by *2024-02-21*.
>   * If you have any questions or require clarification on specific
>     items,?please don't hesitate to reach out to the product team.
>   * Submit any remaining P1 and P2 bug fixes following the established
>     process.
> 
> By adhering to these deadlines, we can maintain a clear development path 
> and deliver a high-quality product on time. Your timely cooperation is 
> greatly appreciated.
> 
> Thank you for your continued support of SUSE Linux Enterprise.
> 
> Sincerely,
> 
> 
> -- 
> *Radoslav Tsvetkov*
> Senior Program Manager SUSE BCL Linux 
> <https://www.suse.com/solutions/business-critical-linux/>

From lance.ortiz at suse.com  Fri Feb  9 17:25:04 2024
From: lance.ortiz at suse.com (Lance Ortiz)
Date: Fri, 9 Feb 2024 10:25:04 -0700
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
Message-ID: <CAC5Do2WLDfCMtwDXMQiQUb70Tbpe=-kN+SVFjoH3h7PP8W-MYA@mail.gmail.com>

Also it would be great to have a statement we can share with partners.  I
have partners still asking if they can submit feature requests.

Lance

On Fri, Feb 9, 2024 at 9:49?AM Matthias Brugger <matthias.bgg at gmail.com>
wrote:

> Hi Radoslav,
>
> I think it would make sense to provide this information to the wider
> developer audience (e.g. devel at suse.de), so that everybody is on the
> same page about the kABI freezes.
>
> Regards,
> Matthias
>
> On 2/8/24 14:23, Radoslav Tsvetkov wrote:
> > Dear SLE Stakeholders,
> >
> > This serves as a reminder regarding the upcoming deadline for final
> > acceptance of features and changes for SLE Products. To ensure a smooth
> > development process and product release on schedule, we're aiming for
> > finalization by 2024-03-19.
> >
> > Key information:
> >
> >   * Feature and Change Acceptance Deadline also kABI soft
> >     freeze:*2024-02-29*
> >   * Bug Fix Submissions: We will continue to accept bug fixes after this
> >     deadline, with focus on P1 and P2 severity levels.
> >   * Change Acceptance After Deadline: Due to potential schedule
> >     risks, any feature or feature requests submitted after
> >     *2024-02-29* will require *explicit approval by the Product **CCB
> >     *(Change Control Board).
> >   * Hard kABI Freeze: Please note that we will have a hard kABI freeze
> >     on 2024-03-19. This means, after this date, changes to the
> >     application binary interface will no longer be permitted.
> >
> > What's next?
> >
> >   * Please review all outstanding feature and change requests and
> >     finalize your decisions by *2024-02-21*.
> >   * If you have any questions or require clarification on specific
> >     items, please don't hesitate to reach out to the product team.
> >   * Submit any remaining P1 and P2 bug fixes following the established
> >     process.
> >
> > By adhering to these deadlines, we can maintain a clear development path
> > and deliver a high-quality product on time. Your timely cooperation is
> > greatly appreciated.
> >
> > Thank you for your continued support of SUSE Linux Enterprise.
> >
> > Sincerely,
> >
> >
> > --
> > *Radoslav Tsvetkov*
> > Senior Program Manager SUSE BCL Linux
> > <https://www.suse.com/solutions/business-critical-linux/>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240209/cf6eb7fd/attachment-0001.htm>

From rtsvetkov at suse.com  Tue Feb 13 09:52:58 2024
From: rtsvetkov at suse.com (Radoslav Tsvetkov)
Date: Tue, 13 Feb 2024 10:52:58 +0100
Subject: [ANNOUNCEMENT] SLE15 SP6 Snapshot-202402-1 released
Message-ID: <CAL565ayZTCQMG-b2f0ORLa=8ebUz9NSG0K6+AFE-ri=mXypvVQ@mail.gmail.com>

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!     SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL   !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi,

we are happy to announce Snapshot-202402-1 for SLE 15 SP6. The snapshot
media is only released to our partners in the Partner Beta Program and is
acessible to all members of the Public Beta Program via the Pool channel.
To update, they need to force a refresh via 'sudo zypper ref --force'.


Main Info Page
==============
[SUSE Linux Enterprise Server 15 SP6](
https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP6/SUSE+Linux+Enterprise+Server+15+SP6)
- information on the project, its status and responsibilities as well as
important documents and locations.

Download Links
==============
You can get the Snapshot-202402-1 ISO images from:

- [SLE-15-SP6-Full-Snapshot-202402-1](
http://download.suse.de/install/SLE-15-SP6-Full-Snapshot-202402-1)
- [SLE-15-SP6-Online-Snapshot-202402-1](
http://download.suse.de/install/SLE-15-SP6-Online-Snapshot-202402-1)
- [SLE-15-SP6-Minimal-Snapshot-202402-1](
http://download.suse.de/install/SLE-15-SP6-Minimal-Snapshot-202402-1)

Next Steps
==========
- Submit Deadline for PublicBeta 2024-02-21
- PublicBeta-202402 on 2024-02-29


Important Notice
================

SLE 15 SP6 is labelled as a "Refresh" Service Pack. To learn more about our
"Consolidation/Refresh" model please refer to this [article](
https://www.suse.com/c/how-suse-builds-its-enterprise-linux-distribution-part-4/).
Please take a note that during the beta phase our images will continue to
evolve and we'll add new fetaures untill our Public Beta milestone.

For more details on the project roadmap please head to the [Time page of
the Project Plan](
https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP6/SLE15+SP6+Time+Line+and+Gant+Chart),
which includes more information on each project and release milestone and
their Acceptance Criteria. You can find a detailed SLE 15 SP6 schedule on
[Confluence](
https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP6/Schedule)
as well.

Build Numbers
=============
* SLE-15-SP6-Full:                Build54.1
* SLE-15-SP6-Online:              Build54.1

* SLES15-SP6-BYOS.aarch64-0.9.1-Azure-Build1.55
* SLES15-SP6-BYOS.aarch64-0.9.1-EC2-Build1.57
* SLES15-SP6-BYOS.aarch64-0.9.1-GCE-Build1.57
* SLES15-SP6-BYOS.x86_64-0.9.1-Azure-Build1.55
* SLES15-SP6-BYOS.x86_64-0.9.1-EC2-Build1.57
* SLES15-SP6-BYOS.x86_64-0.9.1-GCE-Build1.57
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-Aliyun-Build1.16
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-Azure-Build1.13
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-EC2-Build1.14
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-GCE-Build1.16
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-OpenStack-Build1.15
* SLES15-SP6-CHOST-BYOS.aarch64-0.9.1-SAP-CCloud-Build1.14
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-Aliyun-Build1.16
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-Azure-Build1.13
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-EC2-Build1.14
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-GCE-Build1.16
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-OpenStack-Build1.15
* SLES15-SP6-CHOST-BYOS.x86_64-0.9.1-SAP-CCloud-Build1.14
* SLES15-SP6-EC2-ECS-HVM.aarch64-0.9.1-Build1.14
* SLES15-SP6-EC2-ECS-HVM.x86_64-0.9.1-Build1.14
* SLES15-SP6-HPC-BYOS.aarch64-0.9.1-Azure-Build1.13
* SLES15-SP6-HPC-BYOS.aarch64-0.9.1-EC2-Build1.15
* SLES15-SP6-HPC-BYOS.aarch64-0.9.1-GCE-Build1.15
* SLES15-SP6-HPC-BYOS.x86_64-0.9.1-Azure-Build1.13
* SLES15-SP6-HPC-BYOS.x86_64-0.9.1-EC2-Build1.15
* SLES15-SP6-HPC-BYOS.x86_64-0.9.1-GCE-Build1.15
* SLES15-SP6-HPC.aarch64-0.9.1-Azure-Build1.14
* SLES15-SP6-HPC.aarch64-0.9.1-EC2-Build1.15
* SLES15-SP6-HPC.aarch64-0.9.1-GCE-Build1.15
* SLES15-SP6-HPC.x86_64-0.9.1-Azure-Build1.14
* SLES15-SP6-HPC.x86_64-0.9.1-EC2-Build1.15
* SLES15-SP6-HPC.x86_64-0.9.1-GCE-Build1.15
* SLES15-SP6-Hardened-BYOS.aarch64-0.9.0-Azure-Build1.13
* SLES15-SP6-Hardened-BYOS.aarch64-0.9.0-EC2-Build1.16
* SLES15-SP6-Hardened-BYOS.aarch64-0.9.0-GCE-Build1.16
* SLES15-SP6-Hardened-BYOS.x86_64-0.9.0-Azure-Build1.13
* SLES15-SP6-Hardened-BYOS.x86_64-0.9.0-EC2-Build1.16
* SLES15-SP6-Hardened-BYOS.x86_64-0.9.0-GCE-Build1.16
* SLES15-SP6-Minimal-Image.aarch64-RaspberryPi-Build4.62
* SLES15-SP6-Minimal-Image.s390x-dasd-Build3.81
* SLES15-SP6-Minimal-Image.s390x-dasd-Cloud-Build3.81
* SLES15-SP6-Minimal-Image.s390x-fba-Build3.81
* SLES15-SP6-Minimal-Image.s390x-fba-Cloud-Build3.81
* SLES15-SP6-Minimal-VM.aarch64-kvm-Build4.62
* SLES15-SP6-Minimal-VM.s390x-Cloud-Build3.81
* SLES15-SP6-Minimal-VM.s390x-kvm-Build3.81
* SLES15-SP6-Minimal-VM.x86_64-Cloud-Build4.62
* SLES15-SP6-Minimal-VM.x86_64-MS-HyperV-Build4.62
* SLES15-SP6-Minimal-VM.x86_64-VMware-Build4.62
* SLES15-SP6-Minimal-VM.x86_64-kvm-and-xen-Build4.62
* SLES15-SP6-SAP-Azure-LI-BYOS.x86_64-0.9.1-Devel-Build1.12
* SLES15-SP6-SAP-Azure-LI-BYOS.x86_64-0.9.1-Production-Build1.12
* SLES15-SP6-SAP-Azure-VLI-BYOS.x86_64-0.9.1-Devel-Build1.12
* SLES15-SP6-SAP-Azure-VLI-BYOS.x86_64-0.9.1-Production-Build1.12
* SLES15-SP6-SAP-BYOS.x86_64-0.9.1-Azure-Build1.56
* SLES15-SP6-SAP-BYOS.x86_64-0.9.1-EC2-Build1.56
* SLES15-SP6-SAP-BYOS.x86_64-0.9.1-GCE-Build1.56
* SLES15-SP6-SAP-Hardened-BYOS.x86_64-0.9.0-Azure-Build1.14
* SLES15-SP6-SAP-Hardened-BYOS.x86_64-0.9.0-EC2-Build1.14
* SLES15-SP6-SAP-Hardened-BYOS.x86_64-0.9.0-GCE-Build1.14
* SLES15-SP6-SAP-Hardened.x86_64-0.9.0-Azure-Build1.14
* SLES15-SP6-SAP-Hardened.x86_64-0.9.0-EC2-Build1.14
* SLES15-SP6-SAP-Hardened.x86_64-0.9.0-GCE-Build1.14
* SLES15-SP6-SAP.x86_64-0.9.1-Azure-Build1.14
* SLES15-SP6-SAP.x86_64-0.9.1-EC2-Build1.14
* SLES15-SP6-SAP.x86_64-0.9.1-GCE-Build1.14
* SLES15-SP6-SAPCAL.x86_64-0.9.1-Azure-Build1.12
* SLES15-SP6-SAPCAL.x86_64-0.9.1-EC2-Build1.12
* SLES15-SP6-SAPCAL.x86_64-0.9.1-GCE-Build1.12
* SLES15-SP6.aarch64-0.9.1-Azure-Basic-Build1.13
* SLES15-SP6.aarch64-0.9.1-Azure-Standard-Build1.13
* SLES15-SP6.aarch64-0.9.1-EC2-Build1.15
* SLES15-SP6.aarch64-0.9.1-GCE-Build1.15
* SLES15-SP6.x86_64-0.9.1-Azure-Basic-Build1.13
* SLES15-SP6.x86_64-0.9.1-Azure-Standard-Build1.13
* SLES15-SP6.x86_64-0.9.1-EC2-Build1.15
* SLES15-SP6.x86_64-0.9.1-GCE-Build1.15



Notable Changes
===============
This milestone features many bug fixes and updates, notable Yast
improvements and the last kernel.


Complete Changelogs
-------------------
[Full Changelog on xcdchk](
http://xcdchk.suse.de/results/SLE-15-SP6-Full-Test/54.1)


Selection of Changes in this Milestone
======================================

Updated kernel
--------------
* kernel-source: 6.4.0-150600.2.13 => 6.4.0-150600.2.16

Updated packages
----------------
* aaa_base: 84.87+git20180409.04c9dae-150300.10.6.2 =>
84.87+git20180409.04c9dae-150300.10.9.1
* adcli: 0.8.2-150400.17.3.1 => 0.8.2-150400.17.6.1
* ant-antlr: 1.10.13-150200.4.15.2 => 1.10.14-150200.4.18.2
* ant-junit: 1.10.13-150200.4.15.2 => 1.10.14-150200.4.18.2
* ant: 1.10.13-150200.4.15.2 => 1.10.14-150200.4.18.2
* apache2-mod_jk: 1.2.49-150100.6.6.1 => 1.2.49-150100.6.9.1
* apache-sshd: 2.7.0-150200.5.5.3 => 2.12.0-150200.5.8.1
* apparmor: 3.1.6-150600.2.3 => 3.1.7-150600.1.1
* augeas: 1.12.0-150400.3.3.6 => 1.14.1-150600.1.1
* baobab: 45.0-150600.1.1 => 45.0-150600.2.1
* brltty: 6.4-150400.4.5.1 => 6.6-150600.1.2
* ccache: 3.4.2-1.9 => 4.9-150600.1.1
* cloud-init: 23.1-150100.8.66.1 => 23.3-150100.8.71.1
* cloud-regionsrv-client: 1.0.0-150000.6.102.1 => 1.0.0-150000.6.105.1
* coccinelle: 1.1.0-150400.1.4 => 1.1.1-150600.1.2
* combustion: 1.2+git7-150600.1.1 => 1.3+git5-150600.1.1
* containerd: 1.7.8-150000.103.1 => 1.7.10-150000.106.1
* cpio: 2.13-150400.1.98 => 2.13-150400.3.6.1
* cpupower: 5.14-150600.13.5 => 6.4.0-150600.1.1
* cross-nvptx-gcc7: 7.5.0+r278197-150000.4.35.1 =>
7.5.0+r278197-150000.4.38.1
* cryptsetup: 2.4.3-150400.3.3.1 => 2.7.0-150600.1.1
* dconf-editor: 45.0.1-150600.1.1 => 45.0.1-150600.2.1
* ecj: 4.18-150200.3.6.4 => 4.23-150200.3.9.1
* enchant-1: 1.6.1-1.57 => 1.6.1-150600.12.1
* eog: 45.1-150600.1.1 => 45.2-150600.1.1
* erlang: 23.3.4.19-150300.3.11.1 => 23.3.4.19-150300.3.14.1
* evolution-data-server: 3.42.5-150400.3.5.4 => 3.50.3-150600.1.1
* evolution: 3.42.4-150400.3.8.2 => 3.50.3-150600.1.1
* fence-agents: 4.13.1+git.1698672892.6f7e4327-150600.1.1 =>
4.13.1+git.1704296072.32469f29-150600.1.1
* file-roller: 43.0-150600.1.1 => 43.1-150600.1.1
* fonts-config: 20200609+git0.42e2b1b-150000.4.10.1 =>
20200609+git0.42e2b1b-150600.18.1
* gcc7: 7.5.0+r278197-150000.4.35.1 => 7.5.0+r278197-150000.4.38.1
* gcr3: 3.41.0-150600.1.2 => 3.41.0-150600.2.1
* ghostscript: 9.52-150000.177.1 => 9.52-150000.180.1
* gjs: 1.78.0-150600.1.1 => 1.78.1-150600.1.1
* glibc: 2.38-150600.3.1 => 2.38-150600.4.1
* glib-networking: 2.70.1-150400.1.6 => 2.78.0-150600.1.1
* gnome-control-center: 45.1+22-150600.1.1 => 45.2-150600.1.1
* gnome-initial-setup: 41.4-150400.1.9 => 45.0-150600.1.1
* gnome-logs: 45.beta-150600.1.1 => 45.beta-150600.2.1
* gnome-settings-daemon: 45.0-150600.1.2 => 45.1-150600.1.1
* gnome-shell: 3.42.3-150400.3.3.1 => 3.50.1-150600.1.1
* gnome-terminal: 3.42.3-150400.3.3.1 => 3.50.1-150600.1.1
* gnome-user-docs: 41.5-150400.3.3.1 => 45.1-150600.1.1
* gnutls: 3.8.1-150600.1.6 => 3.8.3-150600.1.1
* go1.21: 1.21.5-150000.1.18.1 => 1.21.6-150000.1.21.1
* gobject-introspection: 1.78.1-150600.1.1 => 1.78.1-150600.2.1
* google-cloud-sap-agent: 2.1-150100.3.15.1 => 2.8-150100.3.20.1
* google-guice: 4.1-150200.3.4.3 => 5.1.0-150200.3.7.1
* gsettings-desktop-schemas: 45.0-150600.1.2 => 45.0-150600.2.1
* gssproxy: 0.8.2-3.9.1 => 0.8.2-150100.3.12.1
* gstreamer-plugins-bad: 1.22.0-150500.3.20.1 => 1.22.8-150600.1.1
* gstreamer-plugins-base: 1.22.0-150500.3.3.1 => 1.22.8-150600.1.1
* gstreamer-plugins-good: 1.22.0-150500.4.3.1 => 1.22.8-150600.1.1
* gstreamer-plugins-ugly: 1.22.0-150500.3.3.1 => 1.22.8-150600.1.1
* gstreamer: 1.22.0-150500.3.2.3 => 1.22.8-150600.1.1
* gtksourceview: 3.24.11-150400.10.11 => 3.24.11-150600.17.1
* gtkspell: 2.0.16-150400.15.8 => 2.0.16-150600.22.1
* guestfs-tools: 1.48.3-150500.3.3.1 => 1.52.0-150600.1.1
* gvfs: 1.52.1-150600.1.1 => 1.52.2-150600.1.1
* haproxy: 2.8.4+git0.a4ebf9d3b-150600.1.1 =>
2.8.5+git0.aaba8d090-150600.1.1
* hawk2: 2.6.4+git.1702030539.5fb7d91b-150000.3.39.1 =>
2.6.4+git.1702030539.5fb7d91b-150000.3.42.1
* java-11-openjdk: 11.0.21.0-150000.3.107.1 => 11.0.22.0-150000.3.110.1
* java-21-openjdk: 21.0.2.0-150600.1.1 => 21.0.2.0-150600.2.2
* kdump: 2.0.0-150600.1.1 => 2.0.1-150600.1.1
* kexec-tools: 2.0.27-150600.1.6 => 2.0.27-150600.2.1
* kubevirt: 1.1.0-150600.1.20 => 1.1.1-150600.1.4
* libapparmor: 3.1.6-150600.2.2 => 3.1.7-150600.1.1
* libcroco: 0.6.13-150600.16.1 => 0.6.13-150600.17.1
* libcryptopp: 8.6.0-150400.3.3.1 => 8.6.0-150400.3.6.1
* libdvdread: 6.0.0-150000.3.2.1 => 6.1.3-150600.1.1
* libgsf: 1.14.51-150600.1.1 => 1.14.51-150600.2.1
* libguestfs: 1.48.6-150500.3.8.1 => 1.52.0-150600.1.6
* libportal: 0.7.1-150600.1.1 => 0.7.1-150600.2.1
* libpwquality: 1.4.5-150600.1.1 => 1.4.5-150600.2.1
* librest0_7: 0.8.1-150600.1.1 => 0.8.1-150600.2.1
* librsvg: 2.57.0-150600.1.1 => 2.57.1-150600.1.1
* librtas: 2.0.5-150600.1.21 => 2.0.5-150600.2.7
* libsecret: 0.21.1-150600.1.1 => 0.21.2-150600.1.1
* libsoup2: 2.74.3-150600.1.1 => 2.74.3-150600.2.1
* libsoup: 3.0.4-150400.1.6 => 3.4.4-150600.1.1
* libssh: 0.9.6-150400.1.5 => 0.9.8-150400.3.3.1
* libvirt-glib: 4.0.0-150400.1.10 => 5.0.0-150600.1.1
* libxml++: 3.2.0-1.25 => 5.0.3-150600.1.1
* makedumpfile: 1.7.3-150600.1.2 => 1.7.4-150600.1.1
* mdevctl: 1.1.0-150400.1.7 => 1.3.0-150600.1.1
* md_monitor: 6.6-3.3.1 => 6.6+11+gcbb8940-150000.3.6.1
* mobile-broadband-provider-info: 20210805-150400.1.5 => 20230416-150600.1.1
* ModemManager: 1.18.10-150500.1.2 => 1.20.6-150600.1.1
* MozillaFirefox: 115.6.0-150200.152.120.1 => 115.7.0-150200.152.123.1
* MozillaThunderbird: 115.6.0-150200.8.142.2 => 115.7.0-150200.8.145.1
* mutter: 45.1-150600.3.1 => 45.1-150600.4.1
* NetworkManager-applet: 1.24.0-150400.4.3.1 => 1.34.0-150600.1.1
* NetworkManager-branding-SLE: 42.1-150500.12.2 => 42.1-150600.17.1
* NetworkManager-openconnect: 1.2.6-150400.9.11 => 1.2.10-150600.1.2
* NetworkManager-openvpn: 1.8.16-150400.3.3.2 => 1.10.2-150600.1.1
* NetworkManager-pptp: 1.2.8-150400.8.11 => 1.2.12-150600.1.1
* NetworkManager: 1.38.6-150500.3.2.1 => 1.44.2-150600.1.1
* NetworkManager-strongswan: 1.4.5-1.29 => 1.6.0-150600.1.1
* ocaml-findlib: 1.8.1-1.18 => 1.9.5-150600.1.1
* ocaml-rpm-macros: 20211027-150400.1.4 => 20231101-150600.1.1
* ocaml: 4.05.0-13.5 => 4.14.1-150600.1.1
* openconnect: 7.08-6.9.1 => 9.12-150400.15.3.1
* openssl-3: 3.0.8-150500.5.19.1 => 3.0.8-150500.5.24.1
* osinfo-db: 20231027-150600.1.1 => 20231215-150600.1.1
* pam: 1.3.0-150000.6.61.1 => 1.3.0-150000.6.66.1
* pcre2: 10.39-150400.4.9.1 => 10.42-150600.1.11
* perf: 6.4.0.git11125.12710f5acb-150600.1.2 =>
6.4.0.git12999.268d1dcb61-150600.1.1
* perl-Spreadsheet-ParseExcel: 0.65-1.19 => 0.65-150000.3.3.1
* perl-Sys-Virt: 9.8.0-150600.1.1 => 10.0.0-150600.1.1
* postfix-bdb: 3.7.3-150500.3.11.1 => 3.8.4-150600.1.1
* postfix: 3.7.3-150500.3.11.1 => 3.8.4-150600.1.1
* powerpc-utils: 1.3.11-150500.3.6.1 => 1.3.11-150500.3.9.1
* python-instance-billing-flavor-check: 0.0.4-150000.1.6.1 =>
0.0.6-150000.1.9.1
* qemu: 8.1.3-150600.2.2 => 8.2.0-150600.1.6
* rear23a: 2.3.a-19.9 => 2.3.a-150300.21.3.1
* redis7: 7.0.8-150500.3.6.1 => 7.0.8-150500.3.9.1
* rsyslog: 8.2306.0-150400.5.24.1 => 8.2306.0-150400.5.27.1
* s390-tools: 2.30.0-150600.1.2 => 2.31.0-150600.1.2
* samba: 4.19.2+git.328.e4c431e307f-150600.1.22 =>
4.19.4+git.339.acf1ccaa020-150600.1.2
* sanlock: 3.6.0-150000.4.3.1 => 3.8.5-150000.4.6.1
* sap-installation-wizard: 4.6.8-150600.1.1 => 4.6.9-150600.1.1
* sevctl: 0.4.3-150600.1.7 => 0.4.3-150600.2.1
* sg3_utils: 1.48+4.fa9618a-150600.1.1 => 1.48+9.7626b4d-150600.1.1
* slurm: 23.02.6-150500.5.12.1 => 23.02.7-150500.5.15.1
* sof-firmware: 2023.09-150600.1.1 => 2023.09.2-150600.1.1
* squid: 6.4-150600.1.19 => 6.6-150600.1.1
* supermin: 5.2.2-150600.6.2 => 5.3.3-150600.1.3
* suse-module-tools: 15.6.6-150600.1.6 => 15.6.7-150600.1.10
* systemd: 254.5-150600.2.9 => 254.8-150600.1.3
* tecla-keyboard-layout-viewer: 45.rc-150600.1.1 => 45.0-150600.1.1
* telepathy-logger: 0.8.2-150600.20.1 => 0.8.2-150600.21.1
* totem: 3.38.2-150400.2.12 => 43.0-150600.1.1
* util-linux: 2.37.4-150500.7.2 => 2.37.4-150500.9.3.1
* vino: 3.22.0-150400.16.11 => 3.22.0-150600.23.1
* virtiofsd: 1.7.2-150600.1.6 => 1.10.1-150600.1.1
* virt-manager: 4.1.0-150600.7.1 => 4.1.0-150600.8.1
* virt-top: 1.0.8-1.56 => 1.1.1-150600.1.1
* vte: 0.66.2-150400.3.2.1 => 0.74.2-150600.1.1
* warewulf4: 4.5.0rc0-150600.1.1 => 4.5.0~rc0-150600.1.3
* xdg-dbus-proxy: 0.1.4-150500.1.1 => 0.1.5-150600.1.1
* xdg-desktop-portal: 1.18.2-150600.1.1 => 1.18.2-150600.2.1
* xorg-x11-server: 21.1.4-150500.7.13.1 => 21.1.4-150500.7.21.1
* xwayland: 22.1.5-150500.7.11.1 => 22.1.5-150500.7.17.1
* yast2-bootloader: 4.6.4-150600.1.1 => 4.6.5-150600.1.1
* yast2-firstboot: 4.6.1-150600.1.1 => 4.6.3-150600.1.1
* yast2-http-server: 4.6.0-150600.1.1 => 4.6.1-150600.1.1
* yast2-installation: 4.6.8-150600.1.1 => 4.6.10-150600.1.1
* yast2-network: 4.6.7-150600.1.1 => 4.6.8-150600.1.1
* yast2-packager: 4.5.17-150500.3.3.1 => 4.6.5-150600.1.1
* yast2-update: 4.6.2-150600.1.1 => 4.6.3-150600.1.1
* zenity: 3.99.90-150600.1.1 => 4.0.0-150600.1.1
* python3-sqlparse: 0.4.2-150300.3.6.1 => 0.4.2-150300.9.1

* grub2: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-arm64-efi: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-i386-pc: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-powerpc-ieee1275: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-s390x-emu: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-snapper-plugin: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-systemd-sleep-plugin: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-x86_64-efi: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* grub2-x86_64-xen: 2.12~rc1-150600.3.9 => 2.12-150600.1.5
* libvisio-0_1-1: 0.1.6-150200.9.2.1 => 0.1.6-150200.8.3.1
* libvisio-devel: 0.1.6-150200.9.2.1 => 0.1.6-150200.8.3.1
* qemu-ipxe: 1.0.0+-150600.2.2 => 1.0.0+-150600.1.6


Added packages
--------------
* apache-commons-jexl 2.1.1
* go1.22 1.22rc2
* jakarta-servlet 5.0.0
* libb2 0.98.1
* libdca 0.0.7+2
* libdvdnav 6.1.1
* libnxz 0.64
* QGnomePlatform-qt6 0.9.1
* qt6-declarative 6.6.1
* snpguest 0.3.2~0
* snphost 0.2.0~0
* tomcat10 10.1.18
* tomcat-jakartaee-migration 1.0.7
* gstreamer-plugins-good
* gstreamer
* libdvdread
* libxml++
* phodav
* spice-gtk
* totem

Removed packages
----------------
* clustduct
* dolly
* gnome-shell-search-provider-gnome-terminal
* go1.20
* go1.20-doc
* go1.20-openssl
* go1.20-openssl-doc
* go1.20-openssl-race
* go1.20-race
* gstreamer-plugins-bad-chromaprint
* libchromaprint1
* libcpupower0
* libcryptsetup12-hmac
* libjson-c3-32bit
* libpcre2-posix2
* libphodav-2_0-0
* libxml++-3_0-1
* lua-genders
* NetworkManager-applet-lang
* NetworkManager-openvpn-gnome
* NetworkManager-strongswan-gnome
* postfix-devel
* wayland-protocols-devel


Changed packages
----------------
None


Resolved and Known Issues
=========================

Notable Known Issues
____________________

SLES: bsc#1218178, bsc#1219289, bsc#1218232 (migration)
SLES s390x: bsc#1219392
SLES SAP:  bsc#1219455, bsc#1218013, bsc#1219359

SLED: bsc#1218935

SLES-HA: bsc#1219261

Resolved
--------
SLES: bsc#1217878, bsc#1217637, bsc#1182303 bsc#1218700, bsc#1218864,
bsc#1217923 (in a maintenance fix)

* For a complete bug list please refer to our [Bugzilla page](
https://bugzilla.suse.com/buglist.cgi?cmdtype=runnamed&list_id=13942414&namedcmd=SLE_15SP6_Triage)



Your SUSE Linux Enterprise Team


-- 
*Radoslav Tsvetkov*
Senior Program Manager SUSE BCL Linux
<https://www.suse.com/solutions/business-critical-linux/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240213/5bf6e0ef/attachment-0001.htm>

From rtsvetkov at suse.com  Tue Feb 13 10:42:41 2024
From: rtsvetkov at suse.com (Radoslav Tsvetkov)
Date: Tue, 13 Feb 2024 11:42:41 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
Message-ID: <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>

Hi Matthias, I'll do thank you for reminding me.

BTW you are replying from your private email. Perhaps that is why I don't
receive your reply. And secondly, how do you get this mail if I do not see
you on the list of sale-release-coord subscribers?

Thanks

Rado

On Fri, Feb 9, 2024 at 5:49?PM Matthias Brugger <matthias.bgg at gmail.com>
wrote:

> Hi Radoslav,
>
> I think it would make sense to provide this information to the wider
> developer audience (e.g. devel at suse.de), so that everybody is on the
> same page about the kABI freezes.
>
> Regards,
> Matthias
>
> On 2/8/24 14:23, Radoslav Tsvetkov wrote:
> > Dear SLE Stakeholders,
> >
> > This serves as a reminder regarding the upcoming deadline for final
> > acceptance of features and changes for SLE Products. To ensure a smooth
> > development process and product release on schedule, we're aiming for
> > finalization by 2024-03-19.
> >
> > Key information:
> >
> >   * Feature and Change Acceptance Deadline also kABI soft
> >     freeze:*2024-02-29*
> >   * Bug Fix Submissions: We will continue to accept bug fixes after this
> >     deadline, with focus on P1 and P2 severity levels.
> >   * Change Acceptance After Deadline: Due to potential schedule
> >     risks, any feature or feature requests submitted after
> >     *2024-02-29* will require *explicit approval by the Product **CCB
> >     *(Change Control Board).
> >   * Hard kABI Freeze: Please note that we will have a hard kABI freeze
> >     on 2024-03-19. This means, after this date, changes to the
> >     application binary interface will no longer be permitted.
> >
> > What's next?
> >
> >   * Please review all outstanding feature and change requests and
> >     finalize your decisions by *2024-02-21*.
> >   * If you have any questions or require clarification on specific
> >     items, please don't hesitate to reach out to the product team.
> >   * Submit any remaining P1 and P2 bug fixes following the established
> >     process.
> >
> > By adhering to these deadlines, we can maintain a clear development path
> > and deliver a high-quality product on time. Your timely cooperation is
> > greatly appreciated.
> >
> > Thank you for your continued support of SUSE Linux Enterprise.
> >
> > Sincerely,
> >
> >
> > --
> > *Radoslav Tsvetkov*
> > Senior Program Manager SUSE BCL Linux
> > <https://www.suse.com/solutions/business-critical-linux/>
>


-- 
*Radoslav Tsvetkov*
Senior Program Manager SUSE BCL Linux
<https://www.suse.com/solutions/business-critical-linux/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240213/4589ecb9/attachment.htm>

From rtsvetkov at suse.com  Tue Feb 13 11:00:34 2024
From: rtsvetkov at suse.com (Radoslav Tsvetkov)
Date: Tue, 13 Feb 2024 12:00:34 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <CAC5Do2WLDfCMtwDXMQiQUb70Tbpe=-kN+SVFjoH3h7PP8W-MYA@mail.gmail.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
 <CAC5Do2WLDfCMtwDXMQiQUb70Tbpe=-kN+SVFjoH3h7PP8W-MYA@mail.gmail.com>
Message-ID: <CAL565axikz=mBnVshRY6ZBzs12PL9unfw72dx7dsZE8n5k9iyA@mail.gmail.com>

Hello Lance,
Thank you for the inquiry.

Our team is not providing ready-to-use statements to the partners. The
message should be in a sense*: "All the remaining features that are not
integrated before release candidate 1 will be provided as a maintenance
update starting July" *You can reframe it according to your concrete case
and partner communication.
Please take into account that no *significant* changes in the product are
possible after the PublicBeta. (Significant change is Eg. PostgreSQL
version or glibc are fixed with PublicBeta)

I hope this brings clarity.


On Fri, Feb 9, 2024 at 6:25?PM Lance Ortiz <lance.ortiz at suse.com> wrote:

> Also it would be great to have a statement we can share with partners.  I
> have partners still asking if they can submit feature requests.
>
> Lance
>
> On Fri, Feb 9, 2024 at 9:49?AM Matthias Brugger <matthias.bgg at gmail.com>
> wrote:
>
>> Hi Radoslav,
>>
>> I think it would make sense to provide this information to the wider
>> developer audience (e.g. devel at suse.de), so that everybody is on the
>> same page about the kABI freezes.
>>
>> Regards,
>> Matthias
>>
>> On 2/8/24 14:23, Radoslav Tsvetkov wrote:
>> > Dear SLE Stakeholders,
>> >
>> > This serves as a reminder regarding the upcoming deadline for final
>> > acceptance of features and changes for SLE Products. To ensure a smooth
>> > development process and product release on schedule, we're aiming for
>> > finalization by 2024-03-19.
>> >
>> > Key information:
>> >
>> >   * Feature and Change Acceptance Deadline also kABI soft
>> >     freeze:*2024-02-29*
>> >   * Bug Fix Submissions: We will continue to accept bug fixes after this
>> >     deadline, with focus on P1 and P2 severity levels.
>> >   * Change Acceptance After Deadline: Due to potential schedule
>> >     risks, any feature or feature requests submitted after
>> >     *2024-02-29* will require *explicit approval by the Product **CCB
>> >     *(Change Control Board).
>> >   * Hard kABI Freeze: Please note that we will have a hard kABI freeze
>> >     on 2024-03-19. This means, after this date, changes to the
>> >     application binary interface will no longer be permitted.
>> >
>> > What's next?
>> >
>> >   * Please review all outstanding feature and change requests and
>> >     finalize your decisions by *2024-02-21*.
>> >   * If you have any questions or require clarification on specific
>> >     items, please don't hesitate to reach out to the product team.
>> >   * Submit any remaining P1 and P2 bug fixes following the established
>> >     process.
>> >
>> > By adhering to these deadlines, we can maintain a clear development
>> path
>> > and deliver a high-quality product on time. Your timely cooperation is
>> > greatly appreciated.
>> >
>> > Thank you for your continued support of SUSE Linux Enterprise.
>> >
>> > Sincerely,
>> >
>> >
>> > --
>> > *Radoslav Tsvetkov*
>> > Senior Program Manager SUSE BCL Linux
>> > <https://www.suse.com/solutions/business-critical-linux/>
>>
>

-- 
*Radoslav Tsvetkov*
Senior Program Manager SUSE BCL Linux
<https://www.suse.com/solutions/business-critical-linux/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240213/6dd34ca3/attachment.htm>

From tiwai at suse.de  Tue Feb 13 11:43:07 2024
From: tiwai at suse.de (Takashi Iwai)
Date: Tue, 13 Feb 2024 12:43:07 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
 <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>
Message-ID: <87v86sy4hg.wl-tiwai@suse.de>

On Tue, 13 Feb 2024 11:42:41 +0100,
Radoslav Tsvetkov wrote:
> 
> 
> Hi Matthias, I'll do thank you for reminding me.
> 
> BTW you are replying from your private email. Perhaps that is why I don't
> receive your reply. And secondly, how do you get this mail if I do not see you
> on the list of sale-release-coord subscribers?

I forwarded the mail to Matthias, as it's an important info to be
shared in the team.


thanks,

Takashi

> 
> Thanks
> 
> Rado
> 
> On Fri, Feb 9, 2024 at 5:49?PM Matthias Brugger <matthias.bgg at gmail.com>
> wrote:
> 
>     Hi Radoslav,
>    
>     I think it would make sense to provide this information to the wider
>     developer audience (e.g. devel at suse.de), so that everybody is on the
>     same page about the kABI freezes.
>    
>     Regards,
>     Matthias
>    
>     On 2/8/24 14:23, Radoslav Tsvetkov wrote:
>     > Dear SLE Stakeholders,
>     >
>     > This serves as a reminder regarding the upcoming deadline for final
>     > acceptance of features and changes for SLE Products. To ensure a smooth
>     > development process and product release on schedule, we're aiming for
>     > finalization by 2024-03-19.
>     >
>     > Key information:
>     >
>     >? ?* Feature and Change Acceptance Deadline also kABI soft
>     >? ? ?freeze:*2024-02-29*
>     >? ?* Bug Fix Submissions:?We will continue to accept bug fixes after this
>     >? ? ?deadline,?with focus on P1 and P2 severity levels.
>     >? ?* Change Acceptance After Deadline:?Due to potential schedule
>     >? ? ?risks,?any feature or feature requests submitted after
>     >? ? ?*2024-02-29*?will require *explicit approval by the Product **CCB
>     >? ? ?*(Change Control Board).
>     >? ?* Hard kABI Freeze:?Please note that we will have a hard kABI freeze
>     >? ? ?on 2024-03-19.?This means,?after this date,?changes to the
>     >? ? ?application binary interface will no longer be permitted.
>     >
>     > What's next?
>     >
>     >? ?* Please review all outstanding feature and change requests and
>     >? ? ?finalize your decisions by *2024-02-21*.
>     >? ?* If you have any questions or require clarification on specific
>     >? ? ?items,?please don't hesitate to reach out to the product team.
>     >? ?* Submit any remaining P1 and P2 bug fixes following the established
>     >? ? ?process.
>     >
>     > By adhering to these deadlines, we can maintain a clear development path
>     > and deliver a high-quality product on time. Your timely cooperation is
>     > greatly appreciated.
>     >
>     > Thank you for your continued support of SUSE Linux Enterprise.
>     >
>     > Sincerely,
>     >
>     >
>     > --
>     > *Radoslav Tsvetkov*
>     > Senior Program Manager SUSE BCL Linux
>     > <https://www.suse.com/solutions/business-critical-linux/>
> 
> --
> Radoslav Tsvetkov
> Senior Program Manager SUSE BCL Linux
> [suse]
> 

From aj at suse.com  Tue Feb 13 12:31:19 2024
From: aj at suse.com (Andreas Jaeger)
Date: Tue, 13 Feb 2024 13:31:19 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <87v86sy4hg.wl-tiwai@suse.de>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
 <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>
 <87v86sy4hg.wl-tiwai@suse.de>
Message-ID: <daeaa3f3-7bbf-4bb4-af25-3f4eda95bcd9@suse.com>

On 13/02/2024 12.43, Takashi Iwai wrote:
> On Tue, 13 Feb 2024 11:42:41 +0100,
> Radoslav Tsvetkov wrote:
>>
>> Hi Matthias, I'll do thank you for reminding me.
>>
>> BTW you are replying from your private email. Perhaps that is why I don't
>> receive your reply. And secondly, how do you get this mail if I do not see you
>> on the list of sale-release-coord subscribers?
> I forwarded the mail to Matthias, as it's an important info to be
> shared in the team.

But why did it end on a private email account? That should never happen 
with SUSE emails!

Andreas
-- 
  Andreas Jaeger aj at suse.com Twitter: jaegerandi
   SUSE Software Solutions Germany GmbH, Frankenstr.146, D 90461 N?rnberg
    (HRB 36809,AG N?rnberg) GF: Ivo Totev,Andrew McDonald,Werner Knoblich
     GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From tiwai at suse.de  Tue Feb 13 12:38:37 2024
From: tiwai at suse.de (Takashi Iwai)
Date: Tue, 13 Feb 2024 13:38:37 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <daeaa3f3-7bbf-4bb4-af25-3f4eda95bcd9@suse.com>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
 <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>
 <87v86sy4hg.wl-tiwai@suse.de>
 <daeaa3f3-7bbf-4bb4-af25-3f4eda95bcd9@suse.com>
Message-ID: <87mss4y1wy.wl-tiwai@suse.de>

On Tue, 13 Feb 2024 13:31:19 +0100,
Andreas Jaeger wrote:
> 
> On 13/02/2024 12.43, Takashi Iwai wrote:
> > On Tue, 13 Feb 2024 11:42:41 +0100,
> > Radoslav Tsvetkov wrote:
> >> 
> >> Hi Matthias, I'll do thank you for reminding me.
> >> 
> >> BTW you are replying from your private email. Perhaps that is why I don't
> >> receive your reply. And secondly, how do you get this mail if I do not see you
> >> on the list of sale-release-coord subscribers?
> > I forwarded the mail to Matthias, as it's an important info to be
> > shared in the team.
> 
> But why did it end on a private email account? That should never
> happen with SUSE emails!

My forward was to mbrugger at suse.com.

I guess Matthias wrote a mail from his gmail account mistakenly
(blame the confusing gmail interface).


Takashi

From mbrugger at suse.com  Wed Feb 14 13:50:31 2024
From: mbrugger at suse.com (Matthias Brugger)
Date: Wed, 14 Feb 2024 14:50:31 +0100
Subject: SLE15 SP6: Heads Up: Final Deadline for Feature and Change
 Acceptance
In-Reply-To: <87mss4y1wy.wl-tiwai@suse.de>
References: <CAL565az0wAoDTPLnPoKy+rmt9e+adjdHAJ4frNiN9fsb1bkqyw@mail.gmail.com>
 <766cb558-3965-4950-9b61-96fe3fe55e06@gmail.com>
 <CAL565ayKp7yGqyG7hhC079VzhEgoTyVZUSnuTy9uHvFYXAukWQ@mail.gmail.com>
 <87v86sy4hg.wl-tiwai@suse.de> <daeaa3f3-7bbf-4bb4-af25-3f4eda95bcd9@suse.com>
 <87mss4y1wy.wl-tiwai@suse.de>
Message-ID: <fcadfd96-b3d2-4836-ad4d-6f8bcfa1ec31@suse.com>



On 13/02/2024 13:38, Takashi Iwai wrote:
> On Tue, 13 Feb 2024 13:31:19 +0100,
> Andreas Jaeger wrote:
>>
>> On 13/02/2024 12.43, Takashi Iwai wrote:
>>> On Tue, 13 Feb 2024 11:42:41 +0100,
>>> Radoslav Tsvetkov wrote:
>>>>
>>>> Hi Matthias, I'll do thank you for reminding me.
>>>>
>>>> BTW you are replying from your private email. Perhaps that is why I don't
>>>> receive your reply. And secondly, how do you get this mail if I do not see you
>>>> on the list of sale-release-coord subscribers?
>>> I forwarded the mail to Matthias, as it's an important info to be
>>> shared in the team.
>>
>> But why did it end on a private email account? That should never
>> happen with SUSE emails!
> 
> My forward was to mbrugger at suse.com.
> 
> I guess Matthias wrote a mail from his gmail account mistakenly
> (blame the confusing gmail interface).
> 

Yes, that's exactly what happened, sorry for the mess.

Matthias

From rtsvetkov at suse.com  Tue Feb 20 15:58:03 2024
From: rtsvetkov at suse.com (Radoslav Tsvetkov)
Date: Tue, 20 Feb 2024 16:58:03 +0100
Subject: [ANNOUNCEMENT] SLE15 SP6: PublicBeta release is postponed for a week
Message-ID: <CAL565awgW0PKJRd=3aWDk6fgxNUZ5fs+0vuyZcNYmX2a+haZ8w@mail.gmail.com>

Dear SLE Stakeholders,


In agreement with product management and the QE, the PublicBeta Milestone,
originally planned for the 29th, will be postponed for a week.


The reason is we need an additional week to achieve the required quality.

In particular:

   - The very late removal of the HPC module still needs to be tested and
   eventually revised.
   - Fixing critical bugs in the SAP products requires additional time.
   - The number of changes since Beta3 is great. The build will profit
   significantly from an additional week for testing.


The release team will keep you informed on all current changes. Follow us
on SUSE Linux Enterprise Server 15SP6
<https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP6/SUSE+Linux+Enterprise+Server+15+SP6+Home>



Thank you


-- 
*Radoslav Tsvetkov*
Senior Program Manager SUSE BCL Linux
<https://www.suse.com/solutions/business-critical-linux/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/partner-collaboration/attachments/20240220/7269b36c/attachment.htm>