Open Stack

Hi,

Thanks everyone for the responses, based on them I've proposed a patch 
[1] that moves the cycle highlights task from R-5 week to R-4 week.

[1] https://review.opendev.org/c/openstack/releases/+/855682

Cheers,

Előd


On 2022. 09. 01. 21:52, Sylvain Bauza wrote:
>
>
> Le jeu. 1 sept. 2022 à 18:02, Allison Price <allison at openinfra.dev> a 
> écrit :
>
>     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.
>
>     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.
>
>
> Thanks Allison for replying by clarifying your needs, it helps a lot.
>
> 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.
> 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.
>
> -Sylvain
>
>     Let me know if that helps.
>
>     Thanks,
>     Allison
>
>
>
>>     On Sep 1, 2022, at 7:38 AM, Rajat Dhasmana <rdhasman at redhat.com>
>>     wrote:
>>
>>     Hi Elod,
>>
>>     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
>>     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
>>     include the whole list.
>>
>>
>>     On Thu, Sep 1, 2022 at 7:56 PM Előd Illés <elod.illes at est.tech>
>>     wrote:
>>
>>         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.
>>
>>         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.
>>
>>         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.
>>
>>         Előd
>>
>>
>>         On 2022. 09. 01. 15:54, Sylvain Bauza wrote:
>>>
>>>
>>>         Le mar. 30 août 2022 à 17:45, Előd Illés
>>>         <elod.illes at est.tech> <mailto:elod.illes at est.tech> a écrit :
>>>
>>>             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].)
>>>
>>>
>>>         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.
>>>         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.
>>>
>>>         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 ?
>>>         -Sylvain
>>>
>>>
>>>             [1]https://releases.openstack.org/zed/schedule.html
>>>             [2]https://releases.openstack.org/zed/schedule.html#z-cycle-highlights
>>>             [3]
>>>             https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights
>>>
>>>             Thanks,
>>>
>>>             Előd Illés
>>>             irc: elodilles
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220902/0a277a12/attachment.htm>