[Bug 2065300] [NEW] [SRU] New upstream microrelease .NET 6.0.30 and SDK 6.0.130
Launchpad Bug Tracker
2065300 at bugs.launchpad.net
Wed May 22 19:36:54 UTC 2024
You have been subscribed to a public bug by Mateus Rodrigues de Morais (mateus-morais):
[Impact]
* This correspond to an upstream microrelease (Microsoft Patch Tuesday
microrelease) released on May 14th, 2024.
* It is beneficial for our LTS users to have access to the latest .NET
stack.
[Test Case]
* The package should build successfully in mantic-proposed and jammy-
proposed.
* The packages should be installable on mantic and jammy
on amd64 and arm64 architectures.
* Autopackage tests should pass.
* The usual manual tests that have been seen in the previous microreleases
LP: #2057699, #1996499, #1983380, #2011807 (see Test Case section there).
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]
* dotnet6 was removed from the current development release.
See LP: #2044511 for details.
* 6.0.30 is the version number of the .NET Runtime and 6.0.130 is the version
number of the .NET SDK. The package version only refers to the SDK version
number.
* We are only building the 6.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/
** Affects: dotnet6 (Ubuntu)
Importance: Undecided
Status: New
** Affects: dotnet6 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: dotnet6 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
[SRU] New upstream microrelease .NET 6.0.30 and SDK 6.0.130
https://bugs.launchpad.net/bugs/2065300
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list