Open Stack

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>
> <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/20220901/a2c99a9f/attachment.htm>