<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le jeu. 1 sept. 2022 à 18:02, Allison Price <<a href="mailto:allison@openinfra.dev">allison@openinfra.dev</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">I can jump in from a release marketing perspective. I think that we have some flexibility while still ensuring we have a cohesive plan for October 5. It would be great if cycle highlights can start rolling in now so we can review them incrementally, but I think we can give teams until the end of next week (September 9) or even early the following week (September 13 at the latest) and still meet all of our deadlines. <div><br></div><div>That said, the September 14 deadline would ideally be a hard deadline, so I would like to not push it past that. If we think that makes more sense from a release perspective, we can make it work from a marketing one. </div><div><br></div></div></blockquote><div><br></div><div>Thanks Allison for replying by clarifying your needs, it helps a lot.</div><div><br></div><div>Honestly, I wasn't asking for a two-week delay (matching with RC1), I was just pointing out the difficulties to provide a release document as the exact same time we were rushing into the feature deadline.</div><div>To be clear, shall we accept to punt by one week the cycle highlights delivery deadline, I'd be more than happy with it as personnally I'd target my duty to be done this Monday.</div><div><br></div><div>-Sylvain<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div></div><div>Let me know if that helps. </div><div><br></div><div>Thanks,</div><div>Allison </div><div><br></div><div><br><div><br><blockquote type="cite"><div>On Sep 1, 2022, at 7:38 AM, Rajat Dhasmana <<a href="mailto:rdhasman@redhat.com" target="_blank">rdhasman@redhat.com</a>> wrote:</div><br><div><div dir="ltr">Hi Elod,<div><br></div><div>I share the same concern as Sylvain. In cinder, we have provided an extension of 1 week after the FF to features so we are really</div><div>not sure which changes are going to get in. I can prepare the highlights with the features we already have merged but that won't</div><div>include the whole list.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 1, 2022 at 7:56 PM Előd Illés <<a href="mailto:elod.illes@est.tech" target="_blank">elod.illes@est.tech</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><p>I think the deadline is more like something to connected to
Feature Freeze. ~After Feature Freeze we know what's in the cycle.
If a project requests a Feature Freeze Exception, then of course,
the FF will happen somewhere between official FF date (Milestone
3) and RC1, and hopefully closer to Milestone 3 date than RC1
date.</p><p>I understand that PTLs are busy with reviewing the last feature
patches, but I think this is more like a best effort, too, to
prepare it as soon as possible, after the Feature Freeze.</p><p>I don't know when exactly the Marketing team is processing the
cycle highlights, but I guess they also handles these a bit
flexible way. Probably to generally state that highlights are only
needed by RC1 would give them much less time, more postponed /
missing docs handling / more hurry. So while I think we have a bit
of a flexibility with the deadline (1-2 working days don't really
count), the best is to try to prepare it as soon as possible.
Anyone from the Marketing team or from Release team, correct me if
i'm wrong.<br>
<br>
Előd</p>
<div><br>
</div>
<div>On 2022. 09. 01. 15:54, Sylvain Bauza
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le mar. 30 août 2022
à 17:45, Előd Illés <a href="mailto:elod.illes@est.tech" target="_blank"><elod.illes@est.tech></a> a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<pre>Hi,
This is a reminder, that *this week* is the week for Cycle highlights
[1][2]! They need to be added to deliverable yamls so that they can be
included in release marketing preparations. (See the details about how
to add them at the project team guide [3].)
</pre>
</div>
</blockquote>
<div><br>
</div>
<div>I'm confused. If I read correctly [3] it says that cycle
highlights can be delivered at RC1 which makes sense to me
as it's post-FeatureFreeze.</div>
<div>Asking for cycle highlights the week of the FeatureFreeze
is both counterproductive and non-logic : While some changes
are still on debate and while we're not yet done with
merging features, we need to write a document saying what
we'll get.</div>
<div><br>
</div>
<div>Couldn't we officially accept the projects to provide
their highlights only at RC1 ? Is it a marketing problem
because RC1 is closer to the GA ?<br>
</div>
<div>-Sylvain<br>
</div>
<div><br>
</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<pre>[1] <a href="https://releases.openstack.org/zed/schedule.html" target="_blank">https://releases.openstack.org/zed/schedule.html</a>
[2] <a href="https://releases.openstack.org/zed/schedule.html#z-cycle-highlights" target="_blank">https://releases.openstack.org/zed/schedule.html#z-cycle-highlights</a>
[3]
<a href="https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights" target="_blank">https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights</a>
Thanks,
Előd Illés
irc: elodilles</pre>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div></div>