From daniela.giri at suse.com Mon Mar 3 15:29:17 2025 From: daniela.giri at suse.com (Daniela Giri) Date: Mon, 3 Mar 2025 16:29:17 +0100 Subject: Beta Programs: Changes to Partner Management Process Message-ID: Hello all, This is to inform you that we are reviewing the entire Beta program process to make it more effective and less error-prone. Among the actions identified, we have decided to deprecate the current Google Sheet listing the Partners we were using for announcements and replace it with a Mailman list, "bcl-beta-partners " which has been configured to be security-compliant. In particular, this will ensure that no partner has visibility of the other participants and cannot make any postings to them. In addition, in agreement with @Scott Bahling , the ownership of this new group has been assigned to his team, allowing them to manage it independently and more efficiently. My team, in the role of Beta Managers, will continue to use it for announcements. In line with this request, this is the new process about the distribution of the *registration codes* effective from now: - The Beta Managers team (my team) will continue to request registration codes from SCC and will share them with the Partners Managers team (Scott's team). - Partners Managers team is in charge of managing the new mailing list "bcl-beta-partners" and distributing the registration codes to partners during the *Private Beta *phase - The Beta Managers team will continue handling the distribution of registration codes during the *Public Beta* As mentioned, this new process is effective from now, as we are in the Private Beta phase for SLES16 and the Public Beta phase for SLE15 SP7. Please don't hesitate to reach out to me or my team if you have any questions. Thanks, Daniela -- Daniela Giri Linux Systems Engineering Senior Manager SUSE Software Solutions Italy S.r.l. (M) +39 3450501958 (E) daniela.giri at suse.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From poswald at suse.com Mon Mar 3 16:41:31 2025 From: poswald at suse.com (Philip Oswald) Date: Mon, 3 Mar 2025 09:41:31 -0700 Subject: Beta Programs: Changes to Partner Management Process In-Reply-To: References: Message-ID: Daniela, I manage partners as well but I am not part of Scott Bahlings team. There needs to be provisions made in this situation in the context of the Beta Program. If I work through Scott Bahling then so be it but I will need to be able to have access to the mailing list 'bcl-beta-partners' and the ability to add and remove partners just as I have been able to do with the Google Sheet. -Philip On Mon, Mar 3, 2025 at 8:29?AM Daniela Giri wrote: > Hello all, > > This is to inform you that we are reviewing the entire Beta program > process to make it more effective and less error-prone. > > Among the actions identified, we have decided to deprecate the current Google > Sheet > listing > the Partners we were using for announcements and replace it with a Mailman > list, "bcl-beta-partners > " which has been > configured to be security-compliant. > In particular, this will ensure that no partner has visibility of the > other participants and cannot make any postings to them. > > In addition, in agreement with @Scott Bahling , the > ownership of this new group has been assigned to his team, allowing them to > manage it independently and more efficiently. > My team, in the role of Beta Managers, will continue to use it for > announcements. > > In line with this request, this is the new process about the distribution > of the *registration codes* effective from now: > - The Beta Managers team (my team) will continue to request registration > codes from SCC and will share them with the Partners Managers team (Scott's > team). > - Partners Managers team is in charge of managing the new mailing list > "bcl-beta-partners" and distributing the registration codes to partners > during the *Private Beta *phase > - The Beta Managers team will continue handling the distribution of > registration codes during the *Public Beta* > > As mentioned, this new process is effective from now, as we are in the > Private Beta phase for SLES16 and the Public Beta phase for SLE15 SP7. > Please don't hesitate to reach out to me or my team if you have any > questions. > > Thanks, > Daniela > -- > > Daniela Giri > > Linux Systems Engineering Senior Manager > > SUSE Software Solutions Italy S.r.l. > > > > (M) +39 3450501958 > > (E) daniela.giri at suse.com > > -- > You received this message because you are subscribed to the Google Groups > "partner-collaboration" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to partner-collaboration+unsubscribe at suse.com. > To view this discussion visit > https://groups.google.com/a/suse.com/d/msgid/partner-collaboration/CAL8yU%3Dcoiuz7Th-SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com > > . > For more options, visit https://groups.google.com/a/suse.com/d/optout. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniela.giri at suse.com Mon Mar 3 19:29:40 2025 From: daniela.giri at suse.com (Daniela Giri) Date: Mon, 3 Mar 2025 20:29:40 +0100 Subject: Beta Programs: Changes to Partner Management Process In-Reply-To: References: Message-ID: Thank you Philip, for this clarification. Of course, I see no issue in keeping your current authorizations and granting you access to the 'bcl-beta-partners' mailing list, as well as the ability to add and remove partners. @Scott Bahling , if you're okay with that as well, I will provide Philip with the required access. Please let us know. Thanks, Daniela On Mon, Mar 3, 2025 at 5:41?PM Philip Oswald wrote: > Daniela, > > I manage partners as well but I am not part of Scott Bahlings team. There > needs to be provisions made in this situation in the context of the Beta > Program. If I work through Scott Bahling then so be it but I will need to > be able to have access to the mailing list 'bcl-beta-partners' and the > ability to add and remove partners just as I have been able to do with the > Google Sheet. > > -Philip > > On Mon, Mar 3, 2025 at 8:29?AM Daniela Giri wrote: > >> Hello all, >> >> This is to inform you that we are reviewing the entire Beta program >> process to make it more effective and less error-prone. >> >> Among the actions identified, we have decided to deprecate the current Google >> Sheet >> listing >> the Partners we were using for announcements and replace it with a Mailman >> list, "bcl-beta-partners >> " which has been >> configured to be security-compliant. >> In particular, this will ensure that no partner has visibility of the >> other participants and cannot make any postings to them. >> >> In addition, in agreement with @Scott Bahling , the >> ownership of this new group has been assigned to his team, allowing them to >> manage it independently and more efficiently. >> My team, in the role of Beta Managers, will continue to use it for >> announcements. >> >> In line with this request, this is the new process about the distribution >> of the *registration codes* effective from now: >> - The Beta Managers team (my team) will continue to request registration >> codes from SCC and will share them with the Partners Managers team (Scott's >> team). >> - Partners Managers team is in charge of managing the new mailing list >> "bcl-beta-partners" and distributing the registration codes to partners >> during the *Private Beta *phase >> - The Beta Managers team will continue handling the distribution of >> registration codes during the *Public Beta* >> >> As mentioned, this new process is effective from now, as we are in the >> Private Beta phase for SLES16 and the Public Beta phase for SLE15 SP7. >> Please don't hesitate to reach out to me or my team if you have any >> questions. >> >> Thanks, >> Daniela >> -- >> >> Daniela Giri >> >> Linux Systems Engineering Senior Manager >> >> SUSE Software Solutions Italy S.r.l. >> >> >> >> (M) +39 3450501958 >> >> (E) daniela.giri at suse.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "partner-collaboration" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to partner-collaboration+unsubscribe at suse.com. >> To view this discussion visit >> https://groups.google.com/a/suse.com/d/msgid/partner-collaboration/CAL8yU%3Dcoiuz7Th-SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com >> >> . >> For more options, visit https://groups.google.com/a/suse.com/d/optout. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbahling at suse.com Tue Mar 4 08:21:36 2025 From: sbahling at suse.com (Scott Bahling) Date: Tue, 04 Mar 2025 09:21:36 +0100 Subject: Beta Programs: Changes to Partner Management Process In-Reply-To: References:

Message-ID: <5ad6bfa454e7f6eb4aab1e0ca6a089f3a0040f1a.camel@suse.com> Hi Daniela, It makes sense to give Philip access to manage his partner accounts. -Scott On Mon, 2025-03-03 at 20:29 +0100, Daniela Giri wrote: > Thank you Philip, for this clarification. > > Of course, I see no issue in keeping your current authorizations and > granting you access to the 'bcl-beta-partners' mailing list, as well as the > ability to add and remove partners. > > @Scott Bahling , if you're okay with that as well, I > will provide Philip with the required access. > Please let us know. > > Thanks, > ?? Daniela > > On Mon, Mar 3, 2025 at 5:41?PM Philip Oswald > wrote: > > > Daniela, > > > > I manage partners as well but I am not part of Scott Bahlings > > team.? There > > needs to be provisions made in this situation in the context of the > > Beta > > Program.? If I work through Scott Bahling then so be it but I will > > need to > > be able to have access to the mailing list 'bcl-beta-partners' and > > the > > ability to add and remove partners just as I have been able to do > > with the > > Google Sheet. > > > > -Philip > > > > On Mon, Mar 3, 2025 at 8:29?AM Daniela Giri > > wrote: > > > > > Hello all, > > > > > > This is to inform you that we are reviewing the entire Beta > > > program > > > process to make it more effective and less error-prone. > > > > > > Among the actions identified, we have decided to deprecate the > > > current Google > > > Sheet > > > < > > > https://docs.google.com/spreadsheets/d/1uiYI2py3zCSICezI0XecWl8ino > > > j_hb3tONFsf0rble4/edit> listing > > > the Partners we were using for announcements and replace it with > > > a Mailman > > > list, "bcl-beta-partners > > > " which > > > has been > > > configured to be security-compliant. > > > In particular, this will ensure that no partner has visibility of > > > the > > > other participants and cannot make any postings to them. > > > > > > In addition, in agreement with @Scott Bahling > > > , the > > > ownership of this new group has been assigned to his team, > > > allowing them to > > > manage it independently and more efficiently. > > > My team, in the role of Beta Managers, will continue to use it > > > for > > > announcements. > > > > > > In line with this request, this is the new process about the > > > distribution > > > of the *registration codes* effective from now: > > > - The Beta Managers team (my team) will continue to request > > > registration > > > codes from SCC and will share them with the Partners Managers > > > team (Scott's > > > team). > > > - Partners Managers team is in charge of managing the new mailing > > > list > > > "bcl-beta-partners" and distributing the registration codes to > > > partners > > > during the *Private Beta *phase > > > - The Beta Managers team will continue handling the distribution > > > of > > > registration codes during the *Public Beta* > > > > > > As mentioned, this new process is effective from now, as we are > > > in the > > > Private Beta phase for SLES16 and the Public Beta phase for SLE15 > > > SP7. > > > Please don't hesitate to reach out to me or my team if you have > > > any > > > questions. > > > > > > Thanks, > > > ?? Daniela > > > -- > > > > > > Daniela Giri > > > > > > Linux Systems Engineering Senior Manager > > > > > > SUSE Software Solutions Italy S.r.l. > > > > > > > > > > > > (M) +39 3450501958 > > > > > > (E) daniela.giri at suse.com > > > > > > -- > > > You received this message because you are subscribed to the > > > Google Groups > > > "partner-collaboration" group. > > > To unsubscribe from this group and stop receiving emails from it, > > > send an > > > email to partner-collaboration+unsubscribe at suse.com. > > > To view this discussion visit > > > https://groups.google.com/a/suse.com/d/msgid/partner-collaboration/CAL8yU%3Dcoiuz7Th-SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com > > > < > > > https://groups.google.com/a/suse.com/d/msgid/partner-collaboration > > > /CAL8yU%3Dcoiuz7Th- > > > SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com?utm_medi > > > um=email&utm_source=footer> > > > . > > > For more options, visit > > > https://groups.google.com/a/suse.com/d/optout. > > > > > From daniela.giri at suse.com Wed Mar 5 10:36:51 2025 From: daniela.giri at suse.com (Daniela Giri) Date: Wed, 5 Mar 2025 11:36:51 +0100 Subject: Beta Programs: Changes to Partner Management Process In-Reply-To: <5ad6bfa454e7f6eb4aab1e0ca6a089f3a0040f1a.camel@suse.com> References:

<5ad6bfa454e7f6eb4aab1e0ca6a089f3a0040f1a.camel@suse.com> Message-ID: Thank you @Scott Bahling , for this confirmation. @Philip Oswald , you have been added as an Administrator for the 'bcl-beta-partners' mailing list. I will send you the password to access it in a separate thread. Thanks all, Daniela On Tue, Mar 4, 2025 at 9:21?AM Scott Bahling wrote: > Hi Daniela, > > It makes sense to give Philip access to manage his partner accounts. > > -Scott > > On Mon, 2025-03-03 at 20:29 +0100, Daniela Giri wrote: > > Thank you Philip, for this clarification. > > > > Of course, I see no issue in keeping your current authorizations and > > granting you access to the 'bcl-beta-partners' mailing list, as well as > the > > ability to add and remove partners. > > > > @Scott Bahling , if you're okay with that as well, I > > will provide Philip with the required access. > > Please let us know. > > > > Thanks, > > Daniela > > > > On Mon, Mar 3, 2025 at 5:41?PM Philip Oswald > > wrote: > > > > > Daniela, > > > > > > I manage partners as well but I am not part of Scott Bahlings > > > team. There > > > needs to be provisions made in this situation in the context of the > > > Beta > > > Program. If I work through Scott Bahling then so be it but I will > > > need to > > > be able to have access to the mailing list 'bcl-beta-partners' and > > > the > > > ability to add and remove partners just as I have been able to do > > > with the > > > Google Sheet. > > > > > > -Philip > > > > > > On Mon, Mar 3, 2025 at 8:29?AM Daniela Giri > > > wrote: > > > > > > > Hello all, > > > > > > > > This is to inform you that we are reviewing the entire Beta > > > > program > > > > process to make it more effective and less error-prone. > > > > > > > > Among the actions identified, we have decided to deprecate the > > > > current Google > > > > Sheet > > > > < > > > > https://docs.google.com/spreadsheets/d/1uiYI2py3zCSICezI0XecWl8ino > > > > j_hb3tONFsf0rble4/edit> listing > > > > the Partners we were using for announcements and replace it with > > > > a Mailman > > > > list, "bcl-beta-partners > > > > " which > > > > has been > > > > configured to be security-compliant. > > > > In particular, this will ensure that no partner has visibility of > > > > the > > > > other participants and cannot make any postings to them. > > > > > > > > In addition, in agreement with @Scott Bahling > > > > , the > > > > ownership of this new group has been assigned to his team, > > > > allowing them to > > > > manage it independently and more efficiently. > > > > My team, in the role of Beta Managers, will continue to use it > > > > for > > > > announcements. > > > > > > > > In line with this request, this is the new process about the > > > > distribution > > > > of the *registration codes* effective from now: > > > > - The Beta Managers team (my team) will continue to request > > > > registration > > > > codes from SCC and will share them with the Partners Managers > > > > team (Scott's > > > > team). > > > > - Partners Managers team is in charge of managing the new mailing > > > > list > > > > "bcl-beta-partners" and distributing the registration codes to > > > > partners > > > > during the *Private Beta *phase > > > > - The Beta Managers team will continue handling the distribution > > > > of > > > > registration codes during the *Public Beta* > > > > > > > > As mentioned, this new process is effective from now, as we are > > > > in the > > > > Private Beta phase for SLES16 and the Public Beta phase for SLE15 > > > > SP7. > > > > Please don't hesitate to reach out to me or my team if you have > > > > any > > > > questions. > > > > > > > > Thanks, > > > > Daniela > > > > -- > > > > > > > > Daniela Giri > > > > > > > > Linux Systems Engineering Senior Manager > > > > > > > > SUSE Software Solutions Italy S.r.l. > > > > > > > > > > > > > > > > (M) +39 3450501958 > > > > > > > > (E) daniela.giri at suse.com > > > > > > > > -- > > > > You received this message because you are subscribed to the > > > > Google Groups > > > > "partner-collaboration" group. > > > > To unsubscribe from this group and stop receiving emails from it, > > > > send an > > > > email to partner-collaboration+unsubscribe at suse.com. > > > > To view this discussion visit > > > > > https://groups.google.com/a/suse.com/d/msgid/partner-collaboration/CAL8yU%3Dcoiuz7Th-SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com > > > > < > > > > https://groups.google.com/a/suse.com/d/msgid/partner-collaboration > > > > /CAL8yU%3Dcoiuz7Th- > > > > SyBJE4c7Zy%3DsBHVqmVtDiZS%2BSAqUEv8e52A%40mail.gmail.com?utm_medi > > > > um=email&utm_source=footer> > > > > . > > > > For more options, visit > > > > https://groups.google.com/a/suse.com/d/optout. > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rtsvetkov at suse.com Wed Mar 19 19:56:59 2025 From: rtsvetkov at suse.com (Radoslav Tsvetkov) Date: Wed, 19 Mar 2025 20:56:59 +0100 Subject: [ANNOUNCEMENT] SUSE Linux Enterprise 15 SP7 RC1-202503 is out Message-ID: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Hi, we are happy to announce the RC1-202503 for SLE15 SP7. Please read the limitations of the build at the end of this Email. Main Info Page ============== [SUSE Linux Enterprise Server 15 SP7]( https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP7/SUSE+Linux+Enterprise+Server+15+SP7+Home) - information on the project, its status and responsibilities as well as important documents and locations. Download Links ============== You can get the RC1-202503 ISO images from: - [SLE-15-SP7-Full-RC1-202503]( https://download.nue.suse.com/install/SLE-15-SP7-Full-RC1-202503) - [SLE-15-SP7-Online-RC1-202503]( https://download.nue.suse.com/install/SLE-15-SP7-Online-RC1-202503) - [SLE-15-SP7-Minimal-RC1-202503]( https://download.nue.suse.com/install/SLE-15-SP7-Minimal-RC1-202503/) Also, you'll be able to use the respective mirror sites. Next Steps ========== - A Snapshot - PublicRC-202504 2025-04-17 Important Notice ================ SLE15 SP7 is labeled as a "Consolidation" 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 note that during the beta phase, our images will continue to evolve, and we'll add new features until 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/SUSELinuxEnterpriseServer15SP7/SLE15+SP7+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 SP7 schedule on [Confluence]( https://confluence.suse.com/display/SUSELinuxEnterpriseServer15SP7/Schedule) as well. Build Numbers ============= Builds from SUSE:SLE-15-SP7:GA: * SLE-15-SP7-Full:Build74.1 * SLE-15-SP7-Online:Build74.1 * SLES15-SP7-BYOS.aarch64-0.9.1-Azure-Build1.2 * SLES15-SP7-BYOS.aarch64-0.9.1-EC2-Build1.2 * SLES15-SP7-BYOS.aarch64-0.9.1-GCE-Build1.2 * SLES15-SP7-BYOS.x86_64-0.9.1-Azure-Build1.2 * SLES15-SP7-BYOS.x86_64-0.9.1-EC2-Build1.2 * SLES15-SP7-BYOS.x86_64-0.9.1-GCE-Build1.2 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-Aliyun-Build1.23 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-Azure-Build1.23 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-EC2-Build1.23 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-GCE-Build1.24 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-GDC-Build1.23 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-OpenStack-Build1.23 * SLES15-SP7-CHOST-BYOS.aarch64-0.9.1-SAP-CCloud-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-Aliyun-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-Azure-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-EC2-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-GCE-Build1.24 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-GDC-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-OpenStack-Build1.23 * SLES15-SP7-CHOST-BYOS.x86_64-0.9.1-SAP-CCloud-Build1.23 * SLES15-SP7-EC2-ECS-HVM.aarch64-0.9.1-Build1.2 * SLES15-SP7-EC2-ECS-HVM.x86_64-0.9.1-Build1.2 * SLES15-SP7-HPC-BYOS.aarch64-0.9.1-Azure-Build1.28 * SLES15-SP7-HPC-BYOS.aarch64-0.9.1-EC2-Build1.28 * SLES15-SP7-HPC-BYOS.aarch64-0.9.1-GCE-Build1.28 * SLES15-SP7-HPC-BYOS.x86_64-0.9.1-Azure-Build1.28 * SLES15-SP7-HPC-BYOS.x86_64-0.9.1-EC2-Build1.28 * SLES15-SP7-HPC-BYOS.x86_64-0.9.1-GCE-Build1.28 * SLES15-SP7-HPC.aarch64-0.9.2-Azure-Build1.2 * SLES15-SP7-HPC.aarch64-0.9.2-EC2-Build1.2 * SLES15-SP7-HPC.aarch64-0.9.2-GCE-Build1.2 * SLES15-SP7-HPC.x86_64-0.9.2-Azure-Build1.2 * SLES15-SP7-HPC.x86_64-0.9.2-EC2-Build1.2 * SLES15-SP7-HPC.x86_64-0.9.2-GCE-Build1.2 * SLES15-SP7-Hardened-BYOS.aarch64-0.9.2-Azure-Build1.35 * SLES15-SP7-Hardened-BYOS.aarch64-0.9.2-EC2-Build1.35 * SLES15-SP7-Hardened-BYOS.aarch64-0.9.2-GCE-Build1.35 * SLES15-SP7-Hardened-BYOS.x86_64-0.9.2-Azure-Build1.35 * SLES15-SP7-Hardened-BYOS.x86_64-0.9.2-EC2-Build1.35 * SLES15-SP7-Hardened-BYOS.x86_64-0.9.2-GCE-Build1.35 * SLES15-SP7-Minimal-Image.aarch64-RaspberryPi-Build2.83 * SLES15-SP7-Minimal-Image.s390x-dasd-Build2.83 * SLES15-SP7-Minimal-Image.s390x-dasd-Cloud-Build2.83 * SLES15-SP7-Minimal-Image.s390x-fba-Build2.83 * SLES15-SP7-Minimal-Image.s390x-fba-Cloud-Build2.83 * SLES15-SP7-Minimal-VM.aarch64-Cloud-Build2.83 * SLES15-SP7-Minimal-VM.aarch64-kvm-Build2.83 * SLES15-SP7-Minimal-VM.s390x-Cloud-Build2.83 * SLES15-SP7-Minimal-VM.s390x-kvm-Build2.83 * SLES15-SP7-Minimal-VM.x86_64-Cloud-Build2.83 * SLES15-SP7-Minimal-VM.x86_64-MS-HyperV-Build2.83 * SLES15-SP7-Minimal-VM.x86_64-VMware-Build2.83 * SLES15-SP7-Minimal-VM.x86_64-kvm-and-xen-Build2.83 * SLES15-SP7-SAP-Azure-LI-BYOS.x86_64-0.9.0-Devel-Build1.28 * SLES15-SP7-SAP-Azure-LI-BYOS.x86_64-0.9.0-Production-Build1.28 * SLES15-SP7-SAP-Azure-VLI-BYOS.x86_64-0.9.0-Devel-Build1.28 * SLES15-SP7-SAP-Azure-VLI-BYOS.x86_64-0.9.0-Production-Build1.28 * SLES15-SP7-SAP-BYOS.x86_64-0.9.1-Azure-Build1.2 * SLES15-SP7-SAP-BYOS.x86_64-0.9.1-EC2-Build1.2 * SLES15-SP7-SAP-BYOS.x86_64-0.9.1-GCE-Build1.2 * SLES15-SP7-SAP-Hardened-BYOS.x86_64-0.9.2-Azure-Build1.28 * SLES15-SP7-SAP-Hardened-BYOS.x86_64-0.9.2-EC2-Build1.28 * SLES15-SP7-SAP-Hardened-BYOS.x86_64-0.9.2-GCE-Build1.28 * SLES15-SP7-SAP-Hardened.x86_64-0.9.3-Azure-3P-Build1.2 * SLES15-SP7-SAP-Hardened.x86_64-0.9.3-Azure-Build1.2 * SLES15-SP7-SAP-Hardened.x86_64-0.9.3-EC2-Build1.2 * SLES15-SP7-SAP-Hardened.x86_64-0.9.3-GCE-Build1.2 * SLES15-SP7-SAP.x86_64-0.9.2-Azure-3P-Build1.2 * SLES15-SP7-SAP.x86_64-0.9.2-Azure-Build1.2 * SLES15-SP7-SAP.x86_64-0.9.2-EC2-Build1.2 * SLES15-SP7-SAP.x86_64-0.9.2-GCE-Build1.2 * SLES15-SP7-SAPCAL.x86_64-0.9.2-Azure-Build1.2 * SLES15-SP7-SAPCAL.x86_64-0.9.2-EC2-Build1.2 * SLES15-SP7-SAPCAL.x86_64-0.9.2-GCE-Build1.2 * SLES15-SP7.aarch64-0.9.2-Azure-3P-Build1.2 * SLES15-SP7.aarch64-0.9.2-Azure-Basic-Build1.2 * SLES15-SP7.aarch64-0.9.2-Azure-Standard-Build1.2 * SLES15-SP7.aarch64-0.9.2-EC2-Build1.2 * SLES15-SP7.aarch64-0.9.2-GCE-Build1.2 * SLES15-SP7.x86_64-0.9.2-Azure-3P-Build1.2 * SLES15-SP7.x86_64-0.9.2-Azure-Basic-Build1.2 * SLES15-SP7.x86_64-0.9.2-Azure-Standard-Build1.2 * SLES15-SP7.x86_64-0.9.2-EC2-Build1.2 * SLES15-SP7.x86_64-0.9.2-GCE-Build1.2 Complete Changelogs ------------------- [Full Changelog on xcdchk]( http://xcdchk.suse.de/results/SLE-15-SP7-Full-Test/74.1) Selection of Changes in this Milestone ====================================== The Selection will be available very soon [under the link]( http://xcdchk.suse.de/results/SLE-15-SP7-Full-Test/74.1) Updated Packages since PublicBeta-202502 (Build 66.1) ====================================== * aardvark-dns: 1.11.0-150500.3.6.1 => 1.12.2-150500.3.9.1 * apache-commons-cli: 1.5.0-150200.3.6.4 => 1.9.0-150200.3.9.1 * apache-commons-daemon: 1.3.4-150200.11.14.1 => 1.4.0-150200.11.17.1 * autoyast2: 4.7.0-150700.1.1 => 4.7.1-150700.1.1 * azure-cli: 2.58.0-150400.14.9.1 => 2.58.0-150400.14.12.1 * bcc: 0.32.0-150700.1.2 => 0.32.0-150700.2.1 * bouncycastle: 1.78.1-150200.3.29.1 => 1.79-150200.3.32.2 * btrfsmaintenance: 0.4.2-3.3.1 => 0.4.2-150100.3.6.2 * buildah: 1.35.5-150500.3.25.1 => 1.35.5-150500.3.28.1 * clamav: 1.4.2-150600.18.6.1 => 1.4.2-150600.18.9.3 * container-suseconnect: 2.5.0-150000.4.55.1 => 2.5.0-150000.4.58.1 * crmsh: 4.6.1+20250103.c254272-150600.3.20.2 => 4.6.1+20250225.0e45d69-150600.3.26.2 * crypto-policies: 20230920.570ea89-150600.1.9 => 20230920.570ea89-150600.3.6.5 * csp-billing-adapter: 1.1.0-150400.9.18.2 => 1.2.0-150400.9.28.2 * dnsmasq: 2.90-150400.16.3.1 => 2.90-150400.16.6.2 * docker: 26.1.5_ce-150000.212.1 => 27.5.1_ce-150000.215.3 * dpdk: 23.11.1-150700.1.35 => 24.11.1-150700.1.1 * dpdk-thunderx: 23.11.1-150700.1.32 => 24.11.1-150700.1.1 * dracut: 059+suse.543.g98d7f037-150600.3.14.2 => 059+suse.552.g232957b4-150600.3.17.2 * ed25519-java: 0.3.0-150200.5.3.3 => 0.3.0-150200.5.6.1 * emacs: 27.2-150400.3.20.2 => 27.2-150400.3.26.1 * gnutls: 3.8.3-150600.4.3.1 => 3.8.3-150600.4.6.2 * go1.23: 1.23.5-150000.1.18.1 => 1.23.7-150000.1.24.1 * go1.24: 1.24rc2-150000.1.3.1 => 1.24.1-150000.1.12.1 * google-guest-agent: 20241011.01-150000.1.51.1 => 20250116.00-150000.1.54.1 * google-osconfig-agent: 20250115.01-150000.1.41.1 => 20250115.01-150000.1.44.1 * go: 20250115.01-150000.1.41.1 => 20250115.01-150000.1.44.1 * grub2: 2.12-150700.13.14 => 2.12-150700.15.2 * guestfs-tools: 1.53.5-150700.1.1 => 1.53.7-150700.1.1 * helm: 3.16.3-150000.1.38.1 => 3.17.1-150000.1.41.1 * java-1_8_0-ibm: 1.8.0_sr8.35-150000.3.95.1 => 1.8.0_sr8.40-150000.3.98.1 * java-1_8_0-openjdk: 1.8.0.432-150000.3.100.1 => 1.8.0.442-150000.3.103.2 * jsch: 0.2.15-150200.11.13.1 => 0.2.22-150200.11.16.2 * kdump: 2.0.16-150700.1.1 => 2.0.17-150700.1.1 * kernel-source: 6.4.0-150700.13.3 => 6.4.0-150700.14.2 * kiwi-templates-Minimal: 15.7-150700.1.1 => 15.7-150700.2.1 * krb5: 1.20.1-150600.11.3.1 => 1.20.1-150600.11.8.1 * kubevirt: 1.1.1-150700.9.44 => 1.4.0-150700.1.6 * libguestfs: 1.55.3-150700.1.3 => 1.55.6-150700.1.1 * libnvidia-egl-wayland: 1.1.17-150700.1.2 => 1.1.18-150700.1.1 * libpulp: 0.3.9-150700.1.1 => 0.3.11-150700.1.1 * libstorage-ng: 4.5.231-150700.1.1 => 4.5.242-150700.1.1 * libtasn1: 4.13-150000.4.8.1 => 4.13-150000.4.11.1 * libX11: 1.8.10-150700.1.2 => 1.8.10-150700.2.1 * libx86emu: 3.1-1.23 => 3.7-150700.1.1 * libxkbfile: 1.0.9-1.26 => 1.0.9-150000.3.3.1 * libxml2: 2.12.9-150700.1.3 => 2.12.10-150700.1.1 * libzpc: 1.2.0-150600.1.3 => 1.3.0-150700.1.1 * libzypp: 17.35.19-150600.3.44.1 => 17.36.1-150600.3.47.2 * linuxrc: 7.0.34.0-150700.1.4 => 7.0.34.1-150700.1.1 * lvm2: 2.03.24-150700.1.3 => 2.03.24-150700.4.1 * maven-invoker: 3.1.0-150200.3.4.3 => 3.3.0-150200.3.7.5 * maven-surefire: 3.2.5-150200.3.9.17.1 => 3.5.2-150200.3.9.20.2 * mdadm: 4.3-150600.3.6.2 => 4.4-150700.1.2 * Mesa-demo: 8.3.0-1.33 => 9.0.0-150700.1.1 * Mesa: 24.3.3-150700.88.4 => 24.3.3-150700.91.1 * mksusecd: 3.0-150700.1.4 => 3.5-150700.1.1 * MozillaFirefox: 128.7.0-150200.152.170.1 => 128.8.0-150200.152.173.1 * MozillaThunderbird: 128.6.0-150200.8.197.1 => 128.7.0-150200.8.200.1 * multipath-tools: 0.10.2+117+suse.33411aa-150700.1.3 => 0.10.2+122+suse.51e02cc-150700.1.1 * mutter: 45.3-150600.5.9.1 => 45.3-150700.10.1 * netavark: 1.11.0-150500.3.6.1 => 1.12.2-150500.3.11.1 * netty-tcnative: 2.0.69-150200.3.22.1 => 2.0.70-150200.3.25.1 * nvidia-open-driver-G06-signed-cuda: 565.57.01_k6.4.0_150700.43-150700.1.9 => 570.124.06_k6.4.0_150700.46-150700.1.3 * nvidia-open-driver-G06-signed: 550.144.03_k6.4.0_150700.43-150700.1.5 => 570.124.04_k6.4.0_150700.46-150700.1.3 * nvme-cli: 2.11-150700.1.4 => 2.11+17.g6e09119-150700.1.1 * openssh: 9.6p1-150600.6.12.1 => 9.6p1-150600.6.15.2 * openssl1_1-ibmca: 2.4.1-150700.12.1 => 2.4.1-150700.13.1 * openssl-ibmca-engine: 2.4.1-150700.12.1 => 2.4.1-150700.13.1 * openssl-ibmca-provider: 2.4.1-150700.12.1 => 2.4.1-150700.13.1 * openssl-ibmca: 2.4.1-150700.12.1 => 2.4.1-150700.13.1 * openvswitch: 3.3.1-150700.36.10 => 3.5.0-150700.37.1 * osc: 1.9.0-150400.10.6.1 => 1.9.0-150400.10.9.1 * osinfo-db: 20250124-150700.1.1 => 20250124-150700.2.1 * pacemaker: 2.1.9+20241107.c3b66b02d0-150700.1.19 => 2.1.9+20250218.1d6dcabd78-150700.1.2 * pam_pkcs11: 0.6.10-150600.14.1 => 0.6.10-150600.16.3.1 * pam_u2f: 1.2.0-150600.10.5.1 => 1.2.0-150600.10.8.1 * perl-Bootloader: 1.21-150700.1.1 => 1.24-150700.1.1 * perl-Sys-Virt: 10.9.0-150700.1.2 => 11.0.0-150700.1.1 * pkg-config: 0.29.2-1.436 => 0.29.2-150600.15.3.1 * podman: 4.9.5-150500.3.31.1 => 4.9.5-150500.3.37.1 * polkit-default-privs: 13.2+20250203.3e359e6-150700.1.1 => 13.2+20250219.ec96c6c-150700.1.1 * postgresql15: 15.10-150600.16.9.1 => 15.12-150600.16.14.1 * postgresql16: 16.6-150600.16.10.1 => 16.8-150600.16.15.1 * postgresql17: 17.2-150600.13.5.1 => 17.4-150600.13.10.1 * powerpc-utils: 1.3.13-150700.2.1 => 1.3.13-150700.4.1 * ppc64-diag: 2.7.9-150500.3.8.1 => 2.7.10-150600.6.3.1 * procps: 3.3.17-150000.7.39.1 => 3.3.17-150000.7.42.1 * python311: 3.11.10-150600.3.9.2 => 3.11.11-150600.3.16.2 * python3-M2Crypto: 0.38.0-150600.17.3 => 0.44.0-150600.19.3.1 * python3-numpy: 1.17.3-150400.28.34 => 1.17.3-150400.31.1 * python3: 0.6.4-150600.18.2.3 => 0.6.5-150600.18.5.1 * python-instance-billing-flavor-check: 0.1.1-150000.1.14.1 => 0.1.2-150000.1.17.1 * qemu: 9.2.0-150700.3.2 => 9.2.2-150700.1.1 * release-notes-sle_rt: 15.6.20240228-150700.5.63 => 15.7.20250217-150700.1.8 * release-notes-sles: 15.7.20240912-150700.1.48 => 15.7.20240912-150700.1.57 * rmt-server: 2.18-150700.9.41 => 2.21-150700.1.6 * rpmlint: 1.10-150700.35.5 => 1.10-150700.35.8 * rsync: 3.2.7-150600.3.8.1 => 3.2.7-150600.3.11.1 * rust: 1.83.0-150500.27.27.1 => 1.85.0-150500.27.33.1 * s390-tools: 2.37.0-150700.1.1 => 2.37.0-150700.2.6 * salt: 3006.0-150500.4.44.2 => 3006.0-150700.10.1 * SAPHanaSR-ScaleOut: 0.185.3-150000.45.1 => 0.185.4-150000.48.4 * sap-installation-wizard: 4.7.0-150700.1.1 => 4.7.1-150700.1.1 * saptune: 3.1.4-150400.15.16.2 => 3.1.5-150400.15.19.2 * skopeo: 1.14.4-150300.11.11.1 => 1.14.4-150300.11.19.1 * sled-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-ha-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-basesystem-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-containers-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-desktop-applications-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-development-tools-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-hpc-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-legacy-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-live-patching-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-public-cloud-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-python3-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-rt-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-sap-applications-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-sap-business-one-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-server-applications-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-systems-management-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-transactional-server-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-module-web-scripting-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-rt-hw_en: 15.5-150600.7.35 => 15.7-150700.1.8 * sle-rt-quick_en: 15.5-150600.6.35 => 15.7-150700.1.8 * SLE_RT-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-rt-shielding_en: 15.5-150600.7.35 => 15.7-150700.1.8 * sle-rt-virtguide_en: 15.5-150600.7.35 => 15.7-150700.1.8 * SLES_SAP-release: 15.7-150700.20.1 => 15.7-150700.22.1 * sle-we-release: 15.7-150700.20.1 => 15.7-150700.22.1 * spack: 0.23.0-150700.1.1 => 0.23.1-150400.24.1 * spirv-tools: 2024.4~rc2-150700.1.1 => 2024.4~rc2-150700.2.1 * supportutils-plugin-salt: 1.2.2-150000.3.13.1 => 1.2.3-150000.3.16.1 * systemd: 254.21-150600.4.21.1 => 254.23-150600.4.25.1 * tboot: 20240625_1.11.4-150600.11.3.1 => 20240625_1.11.9-150700.1.1 * tcsh: 6.20.00-4.15.1 => 6.20.00-150000.4.18.2 * trousers: 0.3.15-150600.8.2 => 0.3.15-150600.10.3.1 * tuned: 2.10.0-150600.28.3.1 => 2.25.1.0+git.889387b-150700.1.1 * ucode-intel: 20241112-150200.50.1 => 20250211-150200.53.1 * vim: 9.1.0836-150500.20.18.1 => 9.1.1101-150500.20.21.1 * virt-manager: 5.0.0-150700.3.1 => 5.0.0-150700.5.1 * virt-v2v: 2.7.4-150700.1.1 => 2.7.7-150700.1.1 * webkit2gtk3: 2.46.3-150600.12.21.1 => 2.46.6-150600.12.27.1 * webkit2gtk3-soup2: 2.46.3-150600.12.21.1 => 2.46.6-150600.12.27.1 * webkit2gtk4: 2.46.3-150600.12.21.1 => 2.46.6-150600.12.27.1 * wireshark: 4.2.9-150600.18.17.1 => 4.2.11-150600.18.20.1 * xca: 2.3.0-150600.10.4 => 2.3.0-150600.12.3.1 * xen: 4.20.0_06-150700.2.3 => 4.20.0_08-150700.2.1 * xorg-x11-server: 21.1.15-150700.1.2 => 21.1.15-150700.2.1 * xwayland: 24.1.4-150700.1.5 => 24.1.5-150700.1.1 * yast2-kdump: 4.7.1-150700.1.1 => 4.7.2-150700.1.1 * yast2-network: 4.7.1-150700.1.1 => 4.7.2-150700.1.1 * yast2-samba-client: 4.7.0-150700.1.1 => 4.7.1-150700.1.1 * yast2-schema-default: 4.6.3-150600.1.2 => 4.7.1-150700.1.1 * yast2-storage-ng: 4.7.2-150700.1.1 => 4.7.3-150700.1.1 * yast2-trans: 84.87.20250125.b3ec3b4065-150700.1.1 => 84.87.20250309.5e79bbe193-150700.1.1 * zchunk: 1.1.16-150600.9.3 => 1.5.1-150700.1.1 * zstd: 1.5.5-150600.1.3 => 1.5.7-150700.1.1 * zypper: 1.14.81-150600.10.22.1 => 1.14.84-150600.10.25.2 * python3-netaddr: 0.7.19-1.17 => 0.7.19-150400.9.3.1 Added packages: * gtk4-branding-SLE 15.0 * pgvector 0.8.0 * postgresql16-pgvector 0.8.0 * postgresql17-pgvector 0.8.0 * proftpd 1.3.8b * rust1.84 1.84.0 * rust1.85 1.85.0 * go * Mesa-demo * Mesa * postgresql16 * postgresql17 * python311 * python3 * rust Removed packages: * cargo1.82 * cargo1.83 * kubernetes1.30-client * kubernetes1.30-client-common * libdpdk-24 * libopenvswitch-3_3-0 * libovn-24_03-0 * python3-apache-libcloud * python3-looseversion * python3-salt * rust1.82 * rust1.82-src * rust1.83 * rust1.83-src Known Bugs and Limitations ====================================== Security FIPS is not fully functional. bsc#1239789 No kubernetes-client package available on the images (will be readded in the upcoming Snapshot) bsc#1238353 [ppc64le] Grub append signature size causing PFW validation fail bsc#1236003 [s390x] After upgrade from 15sp4 to sles15sp7 with ha, the system can't bootup bsc#1239615 [hana] [Dell] Kernel panic - not syncing: GHES: Fatal hardware error (GHES panic timeout) bsc#1230905 Amazon web services - All pattern is missing For a complete list, please refer to [bugzilla](https://bugzilla.suse.com/) Your SUSE Linux Enterprise Team -- *Radoslav Tsvetkov* Senior Program Manager SUSE BCL Linux -------------- next part -------------- An HTML attachment was scrubbed... URL: