BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Indri schedule
BEGIN:VEVENT
SUMMARY:Indri R-24
DTSTART:20261005
DTEND:20261010
DTSTAMP:20260710T155520Z
UID:Indri-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-23 (PTG (virtual))
DTSTART:20261012
DTEND:20261017
DTSTAMP:20260710T155520Z
UID:Indri-R-23
DESCRIPTION:PTG (virtual)\n\nFrom 12 to 16 October\, 2026 we’ll have a v
 irtual PTG to plan the 2027.1 Indri release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-22
DTSTART:20261019
DTEND:20261024
DTSTAMP:20260710T155520Z
UID:Indri-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-21
DTSTART:20261026
DTEND:20261031
DTSTAMP:20260710T155520Z
UID:Indri-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-20
DTSTART:20261102
DTEND:20261107
DTSTAMP:20260710T155520Z
UID:Indri-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-19
DTSTART:20261109
DTEND:20261114
DTSTAMP:20260710T155520Z
UID:Indri-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-18 (Indri-1 milestone)
DTSTART:20261116
DTEND:20261121
DTSTAMP:20260710T155520Z
UID:Indri-R-18
DESCRIPTION:Indri-1 milestone\n\n19 November\, 2026 is the Indri-1 milesto
 ne. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-17
DTSTART:20261123
DTEND:20261128
DTSTAMP:20260710T155520Z
UID:Indri-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-16 (2026.2 Hibiscus Cycle-Trailing Release Deadline)
DTSTART:20261130
DTEND:20261205
DTSTAMP:20260710T155520Z
UID:Indri-R-16
DESCRIPTION:2026.2 Hibiscus Cycle-Trailing Release Deadline\n\nAll project
 s following the cycle-trailing release model must release their 2026.2 Hib
 iscus deliverables by 3 December\, 2026.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-15
DTSTART:20261207
DTEND:20261212
DTSTAMP:20260710T155520Z
UID:Indri-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-14
DTSTART:20261214
DTEND:20261219
DTSTAMP:20260710T155520Z
UID:Indri-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-13
DTSTART:20261221
DTEND:20261226
DTSTAMP:20260710T155520Z
UID:Indri-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-12
DTSTART:20261228
DTEND:20270102
DTSTAMP:20260710T155520Z
UID:Indri-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-11
DTSTART:20270104
DTEND:20270109
DTSTAMP:20260710T155520Z
UID:Indri-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-10 (Indri-2 milestone\; Membership Freeze)
DTSTART:20270111
DTEND:20270116
DTSTAMP:20260710T155520Z
UID:Indri-R-10
DESCRIPTION:Indri-2 milestone\n\n14 January\, 2027 is the Indri-2 mileston
 e. See project-specific notes for relevant deadlines.\n\n\n\nMembership Fr
 eeze\n\nProjects must participate in at least two milestones in order to b
 e considered part of the release. Projects made official after the second 
 milestone\, or which fail to produce milestone releases for at least one o
 f the first and second milestones as well as the third milestone\, are the
 refore not considered part of the release for the cycle. This does not app
 ly to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-9
DTSTART:20270118
DTEND:20270123
DTSTAMP:20260710T155520Z
UID:Indri-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-8
DTSTART:20270125
DTEND:20270130
DTSTAMP:20260710T155520Z
UID:Indri-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-7 (Extra-AC freeze)
DTSTART:20270201
DTEND:20270206
DTSTAMP:20260710T155520Z
UID:Indri-R-7
DESCRIPTION:Extra-AC freeze\n\nAll contributions to OpenStack are valuable
 \, but some are not expressed as Gerrit code changes. That allow teams to 
 list active contributors to their projects and who do not have a code cont
 ribution this cycle\, and therefore won’t automatically be considered an
  Active Contributor and allowed to vote. This is done by adding extra-acs 
 to https://opendev.org/openstack/governance/src/branch/master/reference/pr
 ojects.yaml before the Extra-AC freeze date.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-6 (Final release for non-client libraries)
DTSTART:20270208
DTEND:20270213
DTSTAMP:20260710T155520Z
UID:Indri-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:Indri R-5 (Indri-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze)
DTSTART:20270215
DTEND:20270220
DTSTAMP:20260710T155520Z
UID:Indri-R-5
DESCRIPTION:Indri-3 milestone\n\n18 February\, 2027 is the Indri-3 milesto
 ne. See project-specific notes for relevant deadlines.\n\n\n\nFeature free
 ze\n\nThe Indri-3 milestone marks feature freeze for projects following th
 e release:cycle-with-rc model. No featureful patch should be landed 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 their final
  release during this week\, to match feature freeze.\n\n\n\nSoft StringFre
 eze\n\nYou are no longer allowed to accept proposed changes containing mod
 ifications in user-facing strings. Such changes should be rejected by the 
 review team and postponed until the next series development opens (which s
 hould happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter t
 he Indri-3 milestone\, only critical requirements and constraints changes 
 will be allowed. Freezing our requirements list gives packagers downstream
  an opportunity to catch up and prepare packages for everything necessary 
 for distributions of the upcoming release. The requirements remain frozen 
 until the stable branches are created\, with the release candidates.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-4 (Cycle Highlights)
DTSTART:20270222
DTEND:20270227
DTSTAMP:20260710T155520Z
UID:Indri-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: 2025.2 Flamingo Highlights. 20
 26.1 Gazpacho Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-3 (RC1 target week\; Hard StringFreeze)
DTSTART:20270301
DTEND:20270306
DTSTAMP:20260710T155520Z
UID:Indri-R-3
DESCRIPTION:RC1 target week\n\nThe week of 1 March\, 2027 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:Indri R-2
DTSTART:20270308
DTEND:20270313
DTSTAMP:20260710T155520Z
UID:Indri-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Indri R-1 (Final RCs and intermediary releases)
DTSTART:20270315
DTEND:20270320
DTSTAMP:20260710T155520Z
UID:Indri-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 15 March\, 
 2027 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:Indri R+0 (2027.1 Indri release)
DTSTART:20270322
DTEND:20270327
DTSTAMP:20260710T155520Z
UID:Indri-R+0
DESCRIPTION:2027.1 Indri release\n\nThe 2027.1 Indri coordinated release w
 ill happen on Wednesday\, 24 March\, 2027.\n\n
END:VEVENT
END:VCALENDAR