Skip to end of metadata
Go to start of metadata

Releases

Release NameStatusInitial Release DateNext PhaseEOL Date
New DelhiPre-Planning1H24PlanningTBD
MontrealPre-Planning2H23PlanningTBD
LondonPre-Planning1H23PlanningTBD
KyotoPre-Planning2H22PlanningTBD
JakartaPre-Planning1H22PlanningTBD
IstanbulPre-Planning2H21PlanningTBD
HonoluluPre-Planning1H21Planning2H21
GuilinPlanning2H20Requirements Definition1H21
FrankfurtRequirements Definition1H20Development2H20
El AltoDevelopment2H19Current Release1H20
Dublin (doc)Current Release

 

EOL2H19
Casablanca (doc)EOL

 


 

Beijing (doc)EOL

 


 

Amsterdam (doc)EOL

 


 

Status Definitions

StatusMeaning
Pre-PlanningOnly the release name has been determined.
PlanningPre-M0.  The release name has been chosen and tentative milestone dates have been determined.
Requirements DefinitionBetween M0 and M1.  The schedule has been approved and requirements are being documented and prioritized.
DevelopmentAfter M1 but before release. Requirements are being implemented and tested.
Current ReleaseThe approved output of the release process which interested end users should be deploying. This release will be maintained until it is replaced by the next release.
End of Life (EOL)This release has been replaced by a newer release and is no longer supported.

1 Comment

  1. This seems to be in need of updating given the TSC presentation here.  The E,F,G release cadence is changed and, the view needs to look forward several years beyond 2020.