[Bug 2115829] Re: [SRU] New upstream microrelease .NET 8.0.118/8.0.18

[Dominik Viererbe]

** Description changed:

  This is the tracking bug for the .NET 8 July 2025 release.
  
  [Impact]
  
-  * This correspond to an upstream microrelease (Microsoft Patch Tuesday
- microrelease) released on July 8th, 2025.
+  * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025:
+    - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
+    - .NET 9.0.7 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.7.md
+    - .NET 9.0.108 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.108.md
+    - .NET 9.0.7 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
+    - ASP.NET Core 9.0.7 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
  
-  * It is beneficial for our LTS users to have access to the latest .NET
+  * It is beneficial for our LTS users to have access to the latest .NET
  stack.
  
  [Test Case]
  
-  * The package should build successfully in -proposed (respectively).
+  * The package should build successfully in -proposed (respectively).
  
-  * The packages should be installable on jammy, noble, oracular, plucky, questing on
-    amd64, arm64, s390x and ppc64el architectures.
+  * The packages should be installable on jammy, noble, oracular, plucky, questing on
+    amd64, arm64, s390x and ppc64el architectures.
  
-  * Autopackage tests should pass.
+  * Autopackage tests should pass.
  
-  * The usual manual tests that have been seen in the previous microreleases
-    (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).
+  * The usual manual tests that have been seen in the previous microreleases
+    (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).
  
-    Note: The need for manual testing has been largely reduced, because the
-          autopkgtests improvements far exceeds the coverage provided by the
-          mentioned manual test plans.
+    Note: The need for manual testing has been largely reduced, because the
+          autopkgtests improvements far exceeds the coverage provided by the
+          mentioned manual test plans.
  
  [Regression Potential]
  
-  * The upstream testing routine is usually satisfactory, but there is
+  * The upstream testing routine is usually satisfactory, but there is
  always a risk of something breaking.
  
  [Other]
  
  * 8.0.18 is the version number of the .NET Runtime and 8.0.118 is the version
-   number of the .NET SDK. The package version only refers to the SDK version
-   number.
+   number of the .NET SDK. The package version only refers to the SDK version
+   number.
  
  * We are only building the 8.0.1xx feature band, because this is the only
-   feature band that allows building from source. See explanation of feature
-   bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only
+   feature band that allows building from source. See explanation of feature
+   bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only
  
  * Overview of how dotnet is versioned: https://learn.microsoft.com/en-
  us/dotnet/core/versions/

** Description changed:

  This is the tracking bug for the .NET 8 July 2025 release.
  
  [Impact]
  
-  * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025:
-    - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
-    - .NET 9.0.7 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.7.md
-    - .NET 9.0.108 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.108.md
-    - .NET 9.0.7 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
-    - ASP.NET Core 9.0.7 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
+  * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025; see:
+    - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
+    - .NET 9.0.7 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.7.md
+    - .NET 9.0.108 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.108.md
+    - .NET 9.0.7 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
+    - ASP.NET Core 9.0.7 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
  
   * It is beneficial for our LTS users to have access to the latest .NET
  stack.
  
  [Test Case]
  
   * The package should build successfully in -proposed (respectively).
  
   * The packages should be installable on jammy, noble, oracular, plucky, questing on
     amd64, arm64, s390x and ppc64el architectures.
  
   * Autopackage tests should pass.
  
   * The usual manual tests that have been seen in the previous microreleases
     (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).
  
     Note: The need for manual testing has been largely reduced, because the
           autopkgtests improvements far exceeds the coverage provided by the
           mentioned manual test plans.
  
  [Regression Potential]
  
   * The upstream testing routine is usually satisfactory, but there is
  always a risk of something breaking.
  
  [Other]
  
  * 8.0.18 is the version number of the .NET Runtime and 8.0.118 is the version
    number of the .NET SDK. The package version only refers to the SDK version
    number.
  
  * We are only building the 8.0.1xx feature band, because this is the only
    feature band that allows building from source. See explanation of feature
    bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only
  
  * Overview of how dotnet is versioned: https://learn.microsoft.com/en-
  us/dotnet/core/versions/

** Description changed:

  This is the tracking bug for the .NET 8 July 2025 release.
  
  [Impact]
  
   * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025; see:
     - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
-    - .NET 9.0.7 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.7.md
-    - .NET 9.0.108 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.7/9.0.108.md
-    - .NET 9.0.7 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
-    - ASP.NET Core 9.0.7 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A9.0.7%20is%3Aclosed%20label%3Aservicing-approved
+    - .NET 8.0.18 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.18.md
+    - .NET 8.0.118 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.118.md
+    - .NET 8.0.18 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved
+    - ASP.NET Core 8.0.18 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved
  
   * It is beneficial for our LTS users to have access to the latest .NET
  stack.
  
  [Test Case]
  
   * The package should build successfully in -proposed (respectively).
  
   * The packages should be installable on jammy, noble, oracular, plucky, questing on
     amd64, arm64, s390x and ppc64el architectures.
  
   * Autopackage tests should pass.
  
   * The usual manual tests that have been seen in the previous microreleases
     (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).
  
     Note: The need for manual testing has been largely reduced, because the
           autopkgtests improvements far exceeds the coverage provided by the
           mentioned manual test plans.
  
  [Regression Potential]
  
   * The upstream testing routine is usually satisfactory, but there is
  always a risk of something breaking.
  
  [Other]
  
  * 8.0.18 is the version number of the .NET Runtime and 8.0.118 is the version
    number of the .NET SDK. The package version only refers to the SDK version
    number.
  
  * We are only building the 8.0.1xx feature band, because this is the only
    feature band that allows building from source. See explanation of feature
    bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only
  
  * Overview of how dotnet is versioned: https://learn.microsoft.com/en-
  us/dotnet/core/versions/

** Description changed:

  This is the tracking bug for the .NET 8 July 2025 release.
  
  [Impact]
  
   * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025; see:
     - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
     - .NET 8.0.18 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.18.md
     - .NET 8.0.118 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.118.md
     - .NET 8.0.18 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved
     - ASP.NET Core 8.0.18 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved
  
   * It is beneficial for our LTS users to have access to the latest .NET
  stack.
  
  [Test Case]
  
   * The package should build successfully in -proposed (respectively).
  
   * The packages should be installable on jammy, noble, oracular, plucky, questing on
     amd64, arm64, s390x and ppc64el architectures.
  
   * Autopackage tests should pass.
  
   * The usual manual tests that have been seen in the previous microreleases
     (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).
  
     Note: The need for manual testing has been largely reduced, because the
           autopkgtests improvements far exceeds the coverage provided by the
           mentioned manual test plans.
  
  [Regression Potential]
  
-  * The upstream testing routine is usually satisfactory, but there is
- always a risk of something breaking.
+  * The upstream testing routine is usually satisfactory (see for example
+ Microsoft's public Azure Pipeline for .NET related repositories:
+ https://dev.azure.com/dnceng-public/public/_build), but there is always
+ a risk of something breaking.
  
  [Other]
  
  * 8.0.18 is the version number of the .NET Runtime and 8.0.118 is the version
    number of the .NET SDK. The package version only refers to the SDK version
    number.
  
  * We are only building the 8.0.1xx feature band, because this is the only
    feature band that allows building from source. See explanation of feature
    bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only
  
  * Overview of how dotnet is versioned: https://learn.microsoft.com/en-
  us/dotnet/core/versions/

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dotnet8 in Ubuntu.
https://bugs.launchpad.net/bugs/2115829

Title:
  [SRU] New upstream microrelease .NET 8.0.118/8.0.18

Status in dotnet8 package in Ubuntu:
  In Progress
Status in dotnet8 source package in Jammy:
  In Progress
Status in dotnet8 source package in Noble:
  In Progress
Status in dotnet8 source package in Oracular:
  In Progress
Status in dotnet8 source package in Plucky:
  In Progress
Status in dotnet8 source package in Questing:
  In Progress

Bug description:
  This is the tracking bug for the .NET 8 July 2025 release.

  [Impact]

   * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease) released on July 8th, 2025; see:
     - .NET blog entry: https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-july-2025-servicing-updates/
     - .NET 8.0.18 Runtime release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.18.md
     - .NET 8.0.118 SDK release notes: https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.18/8.0.118.md
     - .NET 8.0.18 Runtime changes: https://github.com/dotnet/runtime/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved
     - ASP.NET Core 8.0.18 Runtime changes: https://github.com/dotnet/aspnetcore/issues?q=milestone%3A8.0.18%20is%3Aclosed%20label%3Aservicing-approved

   * It is beneficial for our LTS users to have access to the latest
  .NET stack.

  [Test Case]

   * The package should build successfully in -proposed (respectively).

   * The packages should be installable on jammy, noble, oracular, plucky, questing on
     amd64, arm64, s390x and ppc64el architectures.

   * Autopackage tests should pass.

   * The usual manual tests that have been seen in the previous microreleases
     (see https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md).

     Note: The need for manual testing has been largely reduced, because the
           autopkgtests improvements far exceeds the coverage provided by the
           mentioned manual test plans.

  [Regression Potential]

   * The upstream testing routine is usually satisfactory (see for
  example Microsoft's public Azure Pipeline for .NET related
  repositories: https://dev.azure.com/dnceng-public/public/_build), but
  there is always a risk of something breaking.

  [Other]

  * 8.0.18 is the version number of the .NET Runtime and 8.0.118 is the version
    number of the .NET SDK. The package version only refers to the SDK version
    number.

  * We are only building the 8.0.1xx feature band, because this is the only
    feature band that allows building from source. See explanation of feature
    bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only

  * Overview of how dotnet is versioned: https://learn.microsoft.com/en-
  us/dotnet/core/versions/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2115829/+subscriptions