You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The support-phase property for .NET 7 will transition from preview to go-live on September 13th. Previously, this would have been rc.
The support-phase property for .NET 7 will transition from go-live to sts on November 8th. Previously, this would have been current.
Context
"Current" releases will now be referred to as "Short-term Support (STS)" releases, in obvious contrast to "Long-term Support (LTS)" releases. The duration of the support periods and related policies are not changing.
releases.json
Breaking Changereleases.json is a family of files (and schema) that the .NET Team publishes to enable programatic access to the catalog of .NET releases.
We are making some targeted changes to these files, primarily to reduce user confusion, in response to consistent and broad feedback.
We are making three primary changes, ordered from most to least breaking:
current
value withsts
, in thesupport-phase
property.support-phase
. This will includego-live
, in addition tosts
.release-type
property, with immutable values oflts
orsts
, as appropriate.Timing
The change will be made in two phases:
release-type
property, and .NET 7 EOL date, will be added on July 13th via Add new release labels core#7499.support-phase
property for .NET 7 will transition frompreview
togo-live
on September 13th. Previously, this would have beenrc
.support-phase
property for .NET 7 will transition fromgo-live
tosts
on November 8th. Previously, this would have beencurrent
.Context
"Current" releases will now be referred to as "Short-term Support (STS)" releases, in obvious contrast to "Long-term Support (LTS)" releases. The duration of the support periods and related policies are not changing.
The "Current" term will no longer be used.
See .NET Release Labels for more information.
The text was updated successfully, but these errors were encountered: