#1858 Proposed Fedora 29 schedule
Closed: Fixed 2 years ago Opened 2 years ago by jkurik.

I would like to request review of the Fedora 29 milestones and get your approval to publish it as the official Fedora 29 schedule:

Date Milestone
2018-02-20 Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
2018-05-01 Fedora 28 Release
2018-06-19 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
2018-07-03 Change Checkpoint: Proposal submission deadline (System Wide Changes)
2018-07-11 Mass Rebuild
2018-07-24 Change Checkpoint: Proposal submission deadline (Self Contained Changes)
2018-07-31 Software String Freeze
2018-08-14 Change Checkpoint: Completion deadline (testable)
2018-08-14 Branch Fedora 29 from Rawhide (Rawhide becomes future F30)
2018-08-28 Software Translation Deadline
2018-08-28 Bodhi activation point
2018-08-28 Beta Freeze (*)
2018-08-28 Change Checkpoint: 100% Code Complete Deadline
2018-09-18 Beta Release (Preferred target)
2018-09-25 Beta Release (Target #1)
2018-10-09 Final Freeze (*)
2018-10-23 Fedora 29 Final Release (GA) (Preferred target)
2018-10-30 Fedora 29 Final Release (GA) (Target #1)

Metadata Update from @jkurik:
- Issue tagged with: meeting

2 years ago

Looks reasonable to me. We never really did figure out what to do about the string freezes though.

AGREED: Punt on Proposed Fedora 29 schedule for a week to discuss moving "infra freeze" one day after bodhi activation (+7, 0, 0)

I'm in agreement with this schedule plus the one-day delay on Infra Freeze.

AGREED: Punt on Proposed Fedora 29 schedule for a week to discuss moving "infra freeze" one day after bodhi activation (+7, 0, 0)

Was that actually discussed anywhere? Should we add "infra freeze" into the schedule itself? If we're punting on approving a schedule for it, I think we should.

In today's FESCo meeting, we agreed to accept the F29 schedule as-is. ((+1:5,+0:0,-1:1)

Metadata Update from @jsmith:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @jsmith:
- Issue untagged with: meeting

2 years ago

In today's FESCo meeting, we agreed to accept the F29 schedule as-is. ((+1:5,+0:0,-1:1)

To be clear, my -1 was simply because I wanted the infra freeze listed. I'm fine with the schedule otherwise. :)

Reopening to propose an additional item for the schedule.

In today's Blocker Bugs meeting, item https://bugzilla.redhat.com/show_bug.cgi?id=1567875 came up regarding AppStream data. I think it would make sense for this to be part of the official schedule and treated as a FESCo-blocker. So I propose that we select the 2018-10-10 (one day after Final Freeze) as the date we update the AppStream data in preparation for GA release.

EDIT: Corrected the date to 2018-10-10; it originally read 2018-10-11.

Metadata Update from @sgallagh:
- Issue status updated to: Open (was: Closed)
- Issue tagged with: meeting

2 years ago

Reopening to propose an additional item for the schedule.
In today's Blocker Bugs meeting, item https://bugzilla.redhat.com/show_bug.cgi?id=1567875 came up regarding AppStream data. I think it would make sense for this to be part of the official schedule and treated as a FESCo-blocker. So I propose that we select the 2018-10-11 (one day after Final Freeze) as the date we update the AppStream data in preparation for GA release.

I'm guessing there's no string translation of this data? If not, then +1. If there is, then I'm confused.

I think that translation comes from the AppStream Upstream. @kalev is that correct?

No need for translations, it's all already translated at this point. Just need to extract the appdata files (that include translations) from all the rpms in Fedora and compose them into a big xml file that gnome-software can then consume.

@sgallagh @kalev in what format will the appstream data be prepared? I think we should be explicitly clear about what the expectations are.

Metadata Update from @jkurik:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata