fedora-project-schedule

#92 Docs task updates
Closed: Fixed by bcotton. Opened by pbokoc.

Closed: Fixed
Reopen Issue

Hi, the entire current docs schedule is referencing tools and workflows we haven't been using in years (beats on wiki, publican...) and I think it's best to get rid of it altogether. I threw together something more current; let's try this and adjust for future releases if needed.

Since docs heavily depend on other teams and on their tasks being complete, it's best to tie our milestones to key project milestones. The milestone each task is tied to is shown in the table; I hope it makes sense.

Task Start End Duration
Begin collecting Change release notes 1 day after 1st Change checkpoint (Thu 2019-01-03) - 0
Send out a request for non-Change release notes 1 day after 1st Change checkpoint (Thu 2019-01-03) - 0
Branch guides for upcoming release 1 day after Beta Release Public Availability (Wed 2019-03-27) 0
Branch release notes for upcoming release 1 day after Beta Release Public Availability (Wed 2019-03-27) 0
Send out a call for release notes writers 1 day after Beta Release Public Availability (Wed 2019-03-27) 0
Write release notes for upcoming release 1 day after Beta Release Public Availability (Wed 2019-03-27) 7 days before Final Release Public Availability (GA) (Tue 2019-04-23) 27
Update guides for upcoming release 1 day after Beta Release Public Availability (Wed 2019-03-27) 7 days before Final Release Public Availability (GA) (Tue 2019-04-23) 27
Change release notes: submission deadline Start of Mass Rebuild (Wed 2019-01-30) - 0
Non-Change release notes: submission deadline 7 days before end of Write release notes for upcoming release (Tue 2019-04-16) - 0
String freeze for upcoming release 7 days before Final Release Public Availability (GA) (Tue 2019-04-23) - 0
Generate POT files for translation 7 days before Final Release Public Availability (GA) (Tue 2019-04-23) - 0
Announce availability of POT files to translators 7 days before Final Release Public Availability (GA) (Tue 2019-04-23) - 0
Publish updated guides and release notes on docs.fp.o Final Release Public Availability (GA) (Tue 2019-04-30) - 0

On top of the above, the Final Release Readiness Meeting and Final release Go/No-Go Meeting tasks should apply to us as well. The Beta ones shouldn't since we're not delivering anything for Beta.

The general idea is to aim to be ready a week before GA and to hopefully give translators at least a little bit of time to get started before GA, while still giving docs some time to actually write.

Also, Ben, the Change release notes: submission deadline is basically a task for you, since you're the one opening those issues. If you're not okay with the deadline, adjust it as you need; I picked a date I thought was reasonable but I could be wrong.

@pbokoc this is great, thanks so much for the detail. This all seems to make sense. For the Change release notes: submission deadline, I think I'll just leave that out entirely, since i create the issues as they are approved by FESCo. I'm open to leaving it in if you feel strongly about it.

I also wonder how many non-Change release notes we have. This can be a topic for a separate discussion, but I would think most things that would generate a release note should be filed as a Change.

@bcotton OK, I'm fine with leaving it out.

As for non-Change relnotes, there are a couple every release, usually fewer than 5. One item that appears every release is installer changes, since Anaconda is more or less unique to Fedora so you can't easily find that info elsewhere the same way you can with something like Python. Other than that it's whatever people feel like reporting to us. I'd like that to be a bigger part of the release notes, but changes should definitely come first.

@pbokoc I have a draft F31 schedule that incorporates your feedback. Some of the anchor points aren't quite the way you described because of how the tooling works, but it should work out about the same. Please let me know if you see anything that's wrong.

Metadata Update from @bcotton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.