tox -e venv -- init-series $SERIES $NEXT_SERIES

tox-evenv--make-tracking-padussuri

This email is going out to all PTLs and release liaisons for $SERIES.Welcome to the $SERIES series. On behalf of the release management team, Ijust wanted to say hello and make sure you had the information you needto know what to do and what to expect during this coming release cycle.Release Schedule================If you haven't seen it yet, please take a look at the published schedule forthis cycle:    https://releases.openstack.org/$SERIES/schedule.htmlThat lists all of the major milestones along the way as we work towards thecoordinated release on $release-date.Community-wide deadlines are listed under the "Cross-project events" column.You may notice some projects have added project-specific deadlines under the"Project-specific events" column. That can be done by submitting a patch to theopenstack/releases repo updating the doc/source/$SERIES/schedule.* files, ifyou would like to make sure those deadlines are published somewhere.Countdown Emails================Throughout the cycle, we will be sending regular "countdown" emails to theopenstack-discuss mailing list. If you have filtering set up for mailing listemails, please make sure you are not filtering out subject lines that contain"[release]" and "[ptl]" tags.These countdown emails will contain important updates on upcoming deadlines andinformation about necessary actions throughout the cycle. We try to keep themto a minimum, so earlier on in the cycle they will not be sent weekly, butaround deadline times and especially towards the end of the cycle, these willgo out weekly to make sure everyone has the information they need to get workdone in time. Your attention to these emails would be appreciated. We will tryto keep them short.Deliverables============The release process may be new for a few of you. All official OpenStackdeliverables are released by updating deliverable files in theopenstack/releases repo:    https://opendev.org/openstack/releases/src/branch/master/deliverables/$SERIESPlease take a look at your deliverable files and make sure the release-modelmatches what the team plans to follow for this cycle. This model is a way tocommunicate to downstream consumers what to expect, so the release team usesyour declared model to determine when and how to enforce different steps duringthe cycle.Details on the release models and what they mean, as well as documentation onhow to use the releases repo, can be found in the references section here:    https://releases.openstack.org/index.html#referencesThat has documentation for some of our tooling too. The most important one youmay want to know about is the new-release tooling so you don't need to editthose yaml files directly. That command can be used like this:    tools/new_release.sh $SERIES cinder featureThe last part can be major (major version bump), feature (minor version bump),and bugfix (bugfix, or the Z in X.Y.Z).Reviews=======Because of the strict timing of the cycle schedule, it is important that youreview release patches within some days or usually until Thursdays EOB ifpossible. Please look at the incoming review request emails (sent by gerrit)from openstack/releases repository regularly or at least check your inbox atleast once or twice a week:    https://review.opendev.org/q/project:openstack/releases+reviewer:self+is:openThe above link shows a customised list of release patches that only containspatches that you are added as reviewer. Release managers use a script to addPTLs and release liaisons to their relevant release patches as reviewers.Release Liaisons================If anyone should be added as a release liaison, or removed, just submit a patchto update the data/release_liaisons.yaml file in the openstack/releases repowith current information for your team.Please contact us at any point with any questions. We can be reached on theopenstack-discuss mailing list with the [release] tag, or on IRC in the#openstack-release channel.Thanks for your attention. I hope the $SERIES cycle goes well for everyone.

Welcome back to the release countdown emails! These will be sent atmajor points in the $SERIES development cycle, which should concludewith a final release on $release-date.Development Focus-----------------At this stage in the release cycle, focus should be on planning the$SERIES development cycle, assessing $SERIES community goals and approving$SERIES specs.General Information-------------------$remark-on-series-length. In case you haven't seen it yet, please takea look over the schedule for this release:https://releases.openstack.org/$SERIES/schedule.htmlBy default, the team PTL is responsible for handling the release cycleand approving release requests. This task can (and probably should) bedelegated to release liaisons. Now is a good time to review releaseliaison information for your team and make sure it is up to date:https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yamlBy default, all your team deliverables from the $PREVIOUS_SERIES release arecontinued in $SERIES with a similar release model.Upcoming Deadlines & Dates--------------------------$other-upcoming-event_$SERIES-1 milestone: $milestone1

tox -e venv -- list-deliverables --series $LASTSERIES \    --type trailing --missing-final

Development Focus-----------------The $SERIES-1 milestone is next week, on $milestone1! Project team plansfor the $SERIES cycle should now be solidified.General Information-------------------Libraries need to be released at least once per milestone period. Nextweek, the release team will propose releases for any library which hadchanges but has not been otherwise released since the $LASTSERIES release.PTL's or release liaisons, please watch for these and give a +1 toacknowledge them. If there is some reason to hold off on a release, letus know that as well, by posting a -1. If we do not hear anything at allby the end of the week, we will assume things are OK to proceed.NB: If one of your libraries is still releasing 0.x versions, startthinking about when it will be appropriate to do a 1.0 version. Theversion number does signal the state, real or perceived, of the library,so we strongly encourage going to a full major version once things arein a good and usable state.Upcoming Deadlines & Dates--------------------------$SERIES-1 milestone: $milestone1

tools/aclissues.py../project-config../governance

Development Focus-----------------We are now past the $SERIES-1 milestone. Teams should now be focused onfeature development and completion of goals [0].[0] https://governance.openstack.org/tc/goals/selected/index.htmlGeneral Information-------------------Our next milestone in this development cycle will be $SERIES-2, on$milestone2. This milestone is when we freeze the list of deliverablesthat will be included in the $SERIES final release, so if you plan tointroduce new deliverables in this release, please propose a change toadd an empty deliverable file in the deliverables/$SERIES directory ofthe openstack/releases repository.Now is also generally a good time to look at bugfixes that wereintroduced in the master branch that might make sense to be backportedand released in a stable release.If you have any question around the OpenStack release process, feel freeto ask on this mailing-list or on the #openstack-release channel on IRC.Upcoming Deadlines & Dates--------------------------$SERIES-2 Milestone: $milestone2

Development Focus-----------------The $SERIES-2 milestone will happen in next month, on $milestone2.$SERIES-related specs should now be finalized so that teams can moveto implementation ASAP. Some teams observe specific deadlines onthe second milestone (mostly spec freezes): please refer tohttps://releases.openstack.org/$SERIES/schedule.html for details.General Information-------------------Please remember that libraries need to be released at least once permilestone period. At milestone 2, the release team will propose releasesfor any library that has not been otherwise released since milestone 1.Other non-library deliverables that follow the cycle-with-intermediaryrelease model should have an intermediary release before milestone-2.Those who haven't will be proposed to switch to the cycle-with-rc model,which is more suited to deliverables that are released only once per cycle.At milestone-2 we also freeze the contents of the final release. If youhave a new deliverable that should be included in the final release, youshould make sure it has a deliverable file in:https://opendev.org/openstack/releases/src/branch/master/deliverables/$seriesYou should request a beta release (or intermediary release) for those newdeliverables by milestone-2. We understand some may not be quite readyfor a full release yet, but if you have something minimally viable toget released it would be good to do a 0.x release to exercise the releasetooling for your deliverables. See the MembershipFreeze description formore details: https://releases.openstack.org/$SERIES/schedule.html#$S-mfFinally, now may be a good time for teams to check on any stablereleases that need to be done for your deliverables. If you havebugfixes that have been backported, but no stable release gettingthose. If you are unsure what is out there committed but not released,in the openstack/releases repo, running the command"tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report.Upcoming Deadlines & Dates--------------------------$SERIES-2 Milestone: $milestone2

python3 tools/governance_consistency.py $series $project_yaml_file

Development Focus-----------------The $SERIES-2 milestone is next week, on $milestone2! $SERIES-relatedspecs should now be finalized so that teams can move to implementationASAP. Some teams observe specific deadlines on the second milestone(mostly spec freezes): please refer tohttps://releases.openstack.org/$SERIES/schedule.html for details.General Information-------------------Libraries need to be released at least once per milestone period. Nextweek, the release team will propose releases for any library that has notbeen otherwise released since milestone 1. PTL's and release liaisons,please watch for these and give a +1 to acknowledge them. If there issome reason to hold off on a release, let us know that as well. A +1would be appreciated, but if we do not hear anything at all by the endof the week, we will assume things are OK to proceed.Remember that non-library deliverables that follow thecycle-with-intermediary release model should have an intermediaryrelease before milestone-2. Those who haven't will be proposed to switchto the cycle-with-rc model, which is more suited to deliverables thatare released only once per cycle.Next week is also the deadline to freeze the contents of the finalrelease. All new '$SERIES' deliverables need to have a deliverable filein https://opendev.org/openstack/releases/src/branch/master/deliverablesand need to have done a release by milestone-2.Changes proposing those deliverables for inclusion in $SERIES have beenposted, please update them with an actual release request before themilestone-2 deadline if you plan on including that deliverable in $SERIES,or -1 if you need one more cycle to be ready.Upcoming Deadlines & Dates--------------------------$SERIES-2 Milestone: $milestone2

tox-evenv-- \list-deliverables \--unreleased-sinceYYYY-MM-DD \--modelcycle-with-intermediary \--typeclient-library \--typelibrary \>/tmp/deliverables.log

tools/process_auto_releases.sh $SERIES $(cat /tmp/deliverables.log)

tools/aclissues.py../project-config../governance

Development Focus-----------------We are now past the $SERIES-2 milestone, and entering the last developmentphase of the cycle. Teams should be focused on implementing planned workfor the cycle.Now is a good time to review those plans and reprioritize anything ifneeded based on the what progress has been made and what looks realisticto complete in the next few weeks.General Information-------------------Looking ahead to the end of the release cycle, please be aware of thefeature freeze dates. Those vary depending on deliverable type:* General libraries (except client libraries) need to have their last  feature release before Non-client library freeze ($nclfreeze). Their  stable branches are cut early.* Client libraries (think python-*client libraries) need to have their  last feature release before Client library freeze ($milestone3)* Deliverables following a cycle-with-rc model (that would be most  services) observe a Feature freeze on that same date, $milestone3.  Any feature addition beyond that date should be discussed on the  mailing-list and get PTL approval. After feature freeze, cycle-with-rc  deliverables need to produce a first release candidate (and a stable  branch) before RC1 deadline ($rc1-deadline)* Deliverables following cycle-with-intermediary model can release as  necessary, but in all cases before Final RC deadline ($final-rc-deadline)Upcoming Deadlines & Dates--------------------------Non-client library freeze: $nclfreeze (R-6 week)Client library freeze: $milestone3 (R-5 week)$SERIES-3 milestone: $milestone3 (R-5 week)$other-upcoming-event

./tools/list_weeks.pyt2019-04-152019-10-16

tox-evenv--list-deliverables--unreleased \--modelcycle-with-intermediary \--typehorizon-plugin--typeother--typeservice

General Information-------------------The following cycle-with-intermediary deliverables have not done anyintermediary release yet during this cycle. The cycle-with-rc releasemodel is more suited for deliverables that plan to be released only onceper cycle. As a result, we have proposed[1] to change the release modelfor the following deliverables:[ list of deliverables ][1] https://review.opendev.org/#/q/topic:$series-cwiPTLs and release liaisons for each of those deliverables can either +1the release model change, or propose an intermediary release for thatdeliverable. In absence of answer by the end of R-10 week we'll considerthat the switch to cycle-with-rc is preferable.We also published a proposed release schedule for the upcoming$nextseries cycle. Please check out the separate thread:[ link to thread ]Upcoming Deadlines & Dates--------------------------Non-client library freeze: $nclfreeze (R-6 week)Client library freeze: $milestone3 (R-5 week)$SERIES-3 milestone: $milestone3 (R-5 week)$other-upcoming-event

Development Focus-----------------We are entering the last weeks of the $series development cycle. Fromnow until the final release, we'll send a countdown email like thisevery week.It's probably a good time for teams to take stock of their library andclient work that needs to be completed yet. The non-client library freezeis coming up, followed closely by the client lib freeze. Please planaccordingly to avoid any last minute rushes to get key functionality in.General Information-------------------Next week is the Extra-AC freeze, in preparation for elections. Allcontributions to OpenStack are valuable, but some are not expressed asGerrit code changes. Please list active contributors to your project teamwho do not have a code contribution this cycle, and therefore won'tautomatically be considered an Active Contributor and allowedto vote. This is done by adding extra-acs tohttps://opendev.org/openstack/governance/src/branch/master/reference/projects.yamlbefore the Extra-AC freeze on $extraac.A quick reminder of the upcoming freeze dates. Those vary depending ondeliverable type:* Oslo libraries are entering feature freeze next week, $extraac.* General libraries (except client libraries) need to have their lastfeature release before Non-client library freeze ($nclfreeze). Theirstable branches are cut early.* Client libraries (think python-*client libraries) need to have theirlast feature release before Client library freeze ($milestone3)* Deliverables following a cycle-with-rc model (that would be mostservices) observe a Feature freeze on that same date, $milestone3. Anyfeature addition beyond that date should be discussed on the mailing-listand get PTL approval. After feature freeze, cycle-with-rc deliverablesneed to produce a first release candidate (and a stable branch) beforeRC1 deadline ($rc1-deadline)* Deliverables following cycle-with-intermediary model can release asnecessary, but in all cases before Final RC deadline ($final-rc-deadline)Finally, now is also a good time to start planning what highlights youwant for your deliverables in the cycle highlights. The deadline tosubmit an initial version for those is set to one week after Featurefreeze ($highlights).Background on cycle-highlights:http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.htmlProject Team Guide, Cycle-Highlights:https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlightsjeremy [at] openstack.org/fungi on IRC is available if you needhelp selecting or writing your highlights.Upcoming Deadlines & Dates--------------------------Extra-AC freeze: $extraac (R-7 week)Oslo feature freeze: $extraac (R-7 week)Non-client library freeze: $nclfreeze (R-6 week)Client library freeze: $milestone3 (R-5 week)$SERIES-3 milestone: $milestone3 (R-5 week)Cycle highlights deadline: $highlights (R-4 week)$other-upcoming-event

Development Focus-----------------Work on libraries should be wrapping up, in preparation for the variouslibrary-related deadlines coming up. Now is a good time to make decisionson deferring feature work to the next development cycle in order to beable to focus on finishing already-started feature work.General Information-------------------We are now getting close to the end of the cycle, and will be graduallyfreezing feature work on the various deliverables that make up theOpenStack release.This coming week is the deadline for general libraries (except clientlibraries): their last feature release needs to happen before "Non-clientlibrary freeze" on $nclfreeze. Only bugfixes releases will be allowedbeyond this point.When requesting those library releases, you can also include thestable/$series branching request with the review (as an example, see the"branches" section here:https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/os-brick.yaml#n2In the next weeks we will have deadlines for:* Client libraries (think python-*client libraries), which need to havetheir last feature release before "Client library freeze" ($milestone3)* Deliverables following a cycle-with-rc model (that would be mostservices), which observe a Feature freeze on that same date, $milestone3.Any feature addition beyond that date should be discussed on themailing-list and get PTL approval.As we are getting to the point of creating stable/$series branches, thiswould be a good point for teams to review membership in their$project-stable-maint groups. Once the stable/$series branches are cutfor a repo, the ability to approve any necessary backports into thosebranches for $series will be limited to the members of that stable team.If there are any questions about stable policy or stable team membership,please reach out in the #openstack-stable channel.Upcoming Deadlines & Dates--------------------------Non-client library freeze: $nclfreeze (R-6 week)Client library freeze: $milestone3 (R-5 week)$SERIES-3 milestone: $milestone3 (R-5 week)Cycle Highlights Due: $highlight (R-4 week)$series final release: $release-date$other-upcoming-event

Development Focus-----------------We are getting close to the end of the $series cycle! Next week on$milestone3 is the $series-3 milestone, also known as feature freeze.It's time to wrap up feature work in the services and their clientlibraries, and defer features that won't make it to the $next-series cycle.General Information-------------------This coming week is the deadline for client libraries: their last featurerelease needs to happen before "Client library freeze" on $milestone3.Only bugfix releases will be allowed beyond this point.When requesting those library releases, you can also include thestable/$series branching request with the review. As an example, see the"branches" section here:https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/os-brick.yaml#n2$milestone3 is also the deadline for feature work in all OpenStackdeliverables following the cycle-with-rc model. To help those projectsproduce a first release candidate in time, only bugfixes should be allowedin the master branch beyond this point. Any feature work past that deadlinehas to be raised as a Feature Freeze Exception (FFE) and approved by theteam PTL.Finally, feature freeze is also a good time for submitting a first versionof your cycle-highlights. Cycle highlights are the raw data that helps shapewhat is communicated in press releases and other release activity at theend of the cycle, avoiding direct contacts from marketing folks. Seehttps://docs.openstack.org/project-team-guide/release-management.html#cycle-highlightsfor more details.Upcoming Deadlines & Dates--------------------------$series-3 milestone (feature freeze): $milestone3 (R-5 week)RC1 deadline: $rc1-deadline (R-3 week)Final RC deadline: $final-rc-deadline (R-1 week)Final $SERIES release: $release-date$other-upcoming-event

tox-evenv--list-deliverables--unreleased--typelibrary--typeclient-library

tox-evenv--list-deliverables--unreleased \--modelcycle-with-intermediary \--typehorizon-plugin--typeother--typeservice

Quick reminder that we'll need a release very soon for a number ofdeliverables following a cycle-with-intermediary release model but whichhave not done *any* release yet in the $series cycle:{{list-of-deliverables}}Those should be released ASAP, and in all cases before $rc1-deadline, sothat we have a release to include in the final $series release.

Development Focus-----------------We just passed feature freeze! Until release branches are cut, youshould stop accepting featureful changes to deliverables following thecycle-with-rc release model, or to libraries. Exceptions should bediscussed on separate threads on the mailing-list, and feature freezeexceptions approved by the team's PTL.Focus should be on finding and fixing release-critical bugs, so thatrelease candidates and final versions of the $series deliverables can beproposed, well ahead of the final $series release date.General Information-------------------We are still finishing up processing a few release requests, but the$series release requirements are now frozen. If new library releases areneeded to fix release-critical bugs in $series, you must request aRequirements Freeze Exception (RFE) from the requirements team before wecan do a new release to avoid having something released in $series thatis not actually usable. This is done by posting to the openstack-discussmailing list with a subject line similar to:        [$PROJECT][requirements] RFE requested for $PROJECT_LIBInclude justification/reasoning for why a RFE is needed for this lib.If/when the requirements team OKs the post-freeze update, we can thenprocess a new release.A soft String freeze is now in effect, in order to let the I18N team do thetranslation work in good conditions. In Horizon and the various dashboardplugins, you should stop accepting changes that modify user-visiblestrings. Exceptions should be discussed on the mailing-list. By$rc-final-date this will become a hard string freeze, with no changesin user-visible strings allowed.Actions-------stable/$series branches should be created soon for all not-already-branchedlibraries. You should expect 2-3 changes to be proposed for each: a.gitreview update, a reno update (skipped for projects not using reno),and a tox.ini constraints URL update. Please review those in priorityso that the branch can be functional ASAP.The Prelude section of reno release notes is rendered as the top leveloverview for the release. Any important overall messaging for $serieschanges should be added there to make sure the consumers of your releasenotes see them.Upcoming Deadlines & Dates--------------------------RC1 deadline: $rc1-deadline (R-3 week)Final RC deadline: $final-rc-deadline (R-1 week)Final $SERIES release: $release-date$other-upcoming-event

tox-evenv--list-deliverables--unreleased-sinceYYYY-MM-DD \--modelcycle-with-intermediary \--typehorizon-plugin--typeother--typeservice

Quick reminder that for deliverables following the cycle-with-intermediarymodel, the release team will use the latest $series release available onrelease week.The following deliverables have done a $series release, but it was notrefreshed in the last two months: {{list_of_deliverables}}You should consider making a new one very soon, so that we don't use anoutdated version for the final release.

Development Focus-----------------The Release Candidate (RC) deadline is next Thursday, $rc1-deadline. Workshould be focused on fixing any release-critical bugs.General Information-------------------All deliverables released under a cycle-with-rc model should have a firstrelease candidate by the end of the week, from which a stable/$seriesbranch will be cut. This branch will track the $series release.Once stable/$series has been created, the master branch will be ready toswitch to $next-series development. While the master branch will no longerbe feature-frozen, please prioritize any work necessary for completing$series plans.  Release-critical bugfixes will need to be merged in themaster branch first, then backported to the stable/$series branch beforea new release candidate can be proposed.Actions-------Early in the week, the release team will be proposing RC1 patches for allcycle-with-rc projects, using the latest commit from the master branch.If your team is ready to go for cutting RC1, please let us know byleaving a +1 on these patches.If there are still a few more patches needed before RC1, you can -1 thepatch and update it later in the week with the new commit hash you wouldlike to use. Remember, stable/$series branches will be created with this,so you will want to make sure you have what you need included to avoidneeding to backport changes from the master branch (which willtechnically then be $next-series) to this stable branch for anyadditional RCs before the final release.The release team will also be proposing releases for any deliverablefollowing a cycle-with-intermediary model that has not produced any $seriesrelease so far.Finally, now is a good time to finalize release highlights. Releasehighlights help shape the messaging around the release and make sure thatyour work is properly represented.Upcoming Deadlines & Dates--------------------------RC1 deadline: $rc1-deadline (R-3 week)Final RC deadline: $final-rc-deadline (R-1 week)Final $SERIES release: $release-date$other-upcoming-event

Development Focus-----------------At this point we should have release candidates (RC1 or recent intermediaryrelease) for all the $series deliverables. Teams should be working on anyrelease-critical bugs that would require another RC or intermediary releasebefore the final release.Actions-------Early in the week, the release team will be proposing stable/$series branchcreation for all deliverables that have not branched yet, using the latestavailable $series release as the branch point. If your team is ready to gofor creating that branch, please let us know by leaving a +1 on thesepatches.If you would like to wait for another release before branching, you can -1the patch and update it later in the week with the new release you wouldlike to use. By the end of the week the release team will merge thosepatches though, unless an exception is granted.Once stable/$series branches are created, if a release-critical bug isdetected, you will need to fix the issue in the master branch first, thenbackport the fix to the stable/$series branch before releasing out of thestable/$series branch.After all of the cycle-with-rc projects have branched we will branchdevstack, grenade, and the requirements repos. This will effectively openthem up for $next-series development, though the focus should still be onfinishing up $series until the final release.Opening up the new development cycle is also a good opportunity to teamsto revise their zuul jobs and used nodesets and clean up all unnecessaryones.For projects with translations, watch for any translation patches comingthrough and merge them quickly. A new release should be produced so thattranslations are included in the final $series release.Finally, now is a good time to finalize release notes. In particular,consider adding any relevant "prelude" content. Release notes aretargetted for the downstream consumers of your project, so it would begreat to include any useful information for those that are going to pickup and use or deploy the $series version of your project.Upcoming Deadlines & Dates--------------------------Final RC deadline: $final-rc-deadline (R-1 week)Final $SERIES release: $release-date$other-upcoming-event

tools/add_release_note_links.sh $series

Development Focus-----------------We are on the final mile of the $series development cycle!Remember that the $series final release will include the latest releasecandidate (for cycle-with-rc deliverables) or the latest intermediaryrelease (for cycle-with-intermediary deliverables) available.$final-rc-deadline is the deadline for final $series release candidatesas well as any last cycle-with-intermediary deliverables. We will thenenter a quiet period until we tag the final release on $release-date.Teams should be prioritizing fixing release-critical bugs, before thatdeadline.Otherwise it's time to start planning the $next-series development cycle,including discussing Forum and PTG sessions content, in preparation of$other-upcoming-event.Actions-------Watch for any translation patches coming through on the stable/$seriesbranch and merge them quickly. If you discover a release-critical issue,please make sure to fix it on the master branch first, then backport thebugfix to the stable/$series branch before triggering a new release.Please drop by #openstack-release with any questions or concerns aboutthe upcoming release !Upcoming Deadlines & Dates--------------------------Final $SERIES release: $release-date$other-upcoming-event

Development Focus-----------------We will be releasing the coordinated OpenStack $series release next week,on $release-date. Thanks to everyone involved in the $series cycle!We are now in pre-release freeze, so no new deliverable will be createduntil final release, unless a release-critical regression is spotted.Otherwise, teams attending the PTG in $ptg-location should start to planwhat they will be discussing there, by creating and filling team etherpads.You can access the list of PTG etherpads at:http://ptg.openstack.org/etherpads.htmlGeneral Information-------------------On release day, the release team will produce final versions ofdeliverables following the cycle-with-rc release model, by re-taggingthe commit used for the last RC.A patch doing just that will be proposed. PTLs and release liaisons shouldwatch for that final release patch from the release team. While notrequired, we would appreciate having an ack from each team before weapprove it on the 16th, so that their approval is included in the metadatathat goes onto the signed tag.Upcoming Deadlines & Dates--------------------------Final $SERIES release: $release-date$other-upcoming-event

tools/add_release_note_links.sh $SERIES

tox -e venv -- missing-releases --series $SERIES