BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Gazpacho schedule
BEGIN:VEVENT
SUMMARY:Gazpacho R-25
DTSTART;VALUE=DATE:20251006
DTEND;VALUE=DATE:20251011
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-24
DTSTART;VALUE=DATE:20251013
DTEND;VALUE=DATE:20251018
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-23
DTSTART;VALUE=DATE:20251020
DTEND;VALUE=DATE:20251025
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-22 (PTG (virtual))
DTSTART;VALUE=DATE:20251027
DTEND;VALUE=DATE:20251101
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-22
DESCRIPTION:PTG (virtual)\n\nFrom October 27 to 31\, 2025 we’ll have a v
 irtual PTG to plan the 2026.1 Gazpacho release.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-21
DTSTART;VALUE=DATE:20251103
DTEND;VALUE=DATE:20251108
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-20 (Gazpacho-1 milestone)
DTSTART;VALUE=DATE:20251110
DTEND;VALUE=DATE:20251115
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-20
DESCRIPTION:Gazpacho-1 milestone\n\nNovember 13\, 2025 is the Gazpacho-1 m
 ilestone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-19
DTSTART;VALUE=DATE:20251117
DTEND;VALUE=DATE:20251122
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-18
DTSTART;VALUE=DATE:20251124
DTEND;VALUE=DATE:20251129
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-17 (2025.2 Flamingo Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20251201
DTEND;VALUE=DATE:20251206
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-17
DESCRIPTION:2025.2 Flamingo Cycle-Trailing Release Deadline\n\nAll project
 s following the cycle-trailing release model must release their 2025.2 Fla
 mingo deliverables by December 4\, 2025.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-16
DTSTART;VALUE=DATE:20251208
DTEND;VALUE=DATE:20251213
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-15
DTSTART;VALUE=DATE:20251215
DTEND;VALUE=DATE:20251220
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-14
DTSTART;VALUE=DATE:20251222
DTEND;VALUE=DATE:20251227
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-13
DTSTART;VALUE=DATE:20251229
DTEND;VALUE=DATE:20260103
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-12 (Gazpacho-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20260105
DTEND;VALUE=DATE:20260110
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-12
DESCRIPTION:Gazpacho-2 milestone\n\nJanuary 8\, 2026 is the Gazpacho-2 mil
 estone. See project-specific notes for relevant deadlines.\n\n\n\nMembersh
 ip Freeze\n\nProjects must participate in at least two milestones in order
  to be considered part of the release. Projects made official after the se
 cond milestone\, or which fail to produce milestone releases for at least 
 one of the first and second milestones as well as the third milestone\, ar
 e therefore not considered part of the release for the cycle. This does no
 t apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-11
DTSTART;VALUE=DATE:20260112
DTEND;VALUE=DATE:20260117
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-10
DTSTART;VALUE=DATE:20260119
DTEND;VALUE=DATE:20260124
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-9
DTSTART;VALUE=DATE:20260126
DTEND;VALUE=DATE:20260131
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-8
DTSTART;VALUE=DATE:20260202
DTEND;VALUE=DATE:20260207
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-7
DTSTART;VALUE=DATE:20260209
DTEND;VALUE=DATE:20260214
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-7
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20260216
DTEND;VALUE=DATE:20260221
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-5 (Gazpacho-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze)
DTSTART;VALUE=DATE:20260223
DTEND;VALUE=DATE:20260228
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-5
DESCRIPTION:Gazpacho-3 milestone\n\nFebruary 26\, 2026 is the Gazpacho-3 m
 ilestone. See project-specific notes for relevant deadlines.\n\n\n\nFeatur
 e freeze\n\nThe Gazpacho-3 milestone marks feature freeze for projects fol
 lowing the release:cycle-with-rc model. No featureful patch should be land
 ed after this point. Exceptions may be granted by the project PTL.\n\n\n\n
 \n\nFinal release for client libraries\n\nClient libraries should issue th
 eir final release during this week\, to match feature freeze.\n\n\n\nSoft 
 StringFreeze\n\nYou are no longer allowed to accept proposed changes conta
 ining modifications in user-facing strings. Such changes should be rejecte
 d by the review team and postponed until the next series development opens
  (which should happen when RC1 is published).\n\n\n\nRequirements freeze\n
 \nAfter the Gazpacho-3 milestone\, only critical requirements and constrai
 nts changes will be allowed. Freezing our requirements list gives packager
 s downstream an opportunity to catch up and prepare packages for everythin
 g necessary for distributions of the upcoming release. The requirements re
 main frozen until the stable branches are created\, with the release candi
 dates.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-4 (Cycle Highlights)
DTSTART;VALUE=DATE:20260302
DTEND;VALUE=DATE:20260307
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: 2024.1 Caracal Highlights. 202
 4.2 Dalmatian Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20260309
DTEND;VALUE=DATE:20260314
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-3
DESCRIPTION:RC1 target week\n\nThe week of March 9\, 2026 is the target da
 te for projects following the release:cycle-with-rc model to issue their f
 irst release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the 
 RC1 for the project is tagged. At this point\, ideally no strings are chan
 ged (or added\, or removed)\, to give translators time to finish up their 
 efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-2
DTSTART;VALUE=DATE:20260316
DTEND;VALUE=DATE:20260321
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20260323
DTEND;VALUE=DATE:20260328
DTSTAMP:20250710T153222Z
UID:Gazpacho-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of March 23\, 
 2026 is the last week to issue release candidates or intermediary releases
  before release week. During release week\, only final-release-critical re
 leases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Gazpacho R+0 (2026.1 Gazpacho release)
DTSTART;VALUE=DATE:20260330
DTEND;VALUE=DATE:20260404
DTSTAMP:20250710T153222Z
UID:Gazpacho-R+0
DESCRIPTION:2026.1 Gazpacho release\n\nThe 2026.1 Gazpacho coordinated rel
 ease will happen on Wednesday\, April 1\, 2025.\n\n
END:VEVENT
END:VCALENDAR