Note I already included my own draft of the Release Life Cycle page in my set of drafts for the No More Alpha change that I sent to test@ and devel@ for review. We should probably reconcile the two drafts (I haven't checked if/how they differ yet).

I'm going to defer this until next week's meeting while @jkurik and @adamwill reconcile their drafts and to give the rest of FESCo time to weigh in.

For the record, my version of Fedora Release Life Cycle didn't make any actual changes to the schedule, it only removed events that no longer made sense and re-based remaining events that were based on the removed events (but without actually moving them at all). @jkurik 's proposal is actually to change the cycle. So I'd say FESCo can ignore my draft and consider @jkurik 's proposal, and I'll just leave the schedule section of the page out of my no-more-alphas changes entirely and leave it up to this ticket to get it updated.

I have modified the initial proposal and moved "String Freeze" milestone two weeks before Branching (were it always was). Having this milestone just before Beta Freeze was obviously my mistake.

Thanks @pravins and @paragn to point me to this issue.

After some more discussion regarding the "String Freeze" milestone we are in the situation that there is no clear view on timing of this milestone. I have started a discussion with the translation team on mailing list to solve this issue.

For now I would like to ask FESCo to ignore the "String Freeze" milestone and do review of the rest of the proposal, so we have some conclusion how to plan the F28 release. Once the issue with "String Freeze" is clarified with the translation team I will inform FESCo of the outcome.

• AGREED: Update of "Fedora Release Live Cycle" and "Changes / Policy"
  is approved (+8,0,-0) (jforbes, 16:16:58)

I am re-opening this ticket to inform FESCo how "String Freeze milestone" is going to be planned.

After a discussion on trans@ mailing list I am going to update the translation milestones as follows:

• Software String Freeze milestone is going to be planned one week after Branching
• Software Translation Deadline is going to be planned to the same date as Beta Freeze

AGREED: file new ticket on updating the translation policy, make that block the dates/schedule ticket, ask trans and devel for thoughts on new policy, revisit when policy is proposed (+6,0,0) (nirik, 16:31:25)

ACTION: nirik to file new ticket (nirik, 16:31:46)
ACTION: bowlofeggs to start discussion on lists (nirik, 16:33:01)

That new ticket is: https://pagure.io/fesco/issue/1777

Thread started:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TCAOHXFFMF5ZYBKCICMBWM3E5P4TOLYU/

I believe we can close this ticket again, since we are tracking the string freeze milestone in #1777.

Oh, I suppose we were keeping this open until #1777 is done so we can update the schedule here. My apologies for the confusion.

I like @ncoghlan 's proposed reworking of the rain day idea on devel list today.

(LOL copy-paste vs. x buffer fail. Edited to correct link.)

I would like to ask FESCo for review and approval (or comments) to the draft of the Changes Policy and to the draft of the Fedora Release Life Cycle.

I tried to merge together all the changes we were facing during the last time with regards to Changes Policy & Fedora Release Life Cycle. The outcome is available in Changes Policy - DRAFT and Fedora Release Life Cycle - DRAFT.

Basically the changes I did are related to the following topics:

• No More Alphas Change
• Discussion about String Freeze
• Discussion on Rain dates and such
• Feedback from review of these policies
• Removal of description how to build schedule on your own as this
  paragraph was not already valid. I might add some description of this
  later, however I do not think that this belongs to Life Cycle policy
  anyway.
• The Changes Policy - DRAFT also adds a section enforcing work on Release Notes. This is based on my discussion with @bex as a representative of Documentation team. (there will be a follow up on this topic, the part in the policy is just a "top level" part).

There are also available diffs from the currently valid policies:

• Changes Policy - DIFF
• Fedora Release Life Cycle - DIFF

There is also a FESCo ticket #1792 requesting to move Bodhi activation to Beta Freeze. If approved, I can change the Fedora Release Life Cycle accordingly.

I'm +1 to the proposed changes.

AGREED: with addition of 3 weeks for beta freeze and bodhi activation point moving to beta freeze the new release life cycle and changes policy are approved. (+6,0,3) (nirik, 16:40:15)