One of my tasks has been to review the schedule. Of course, we all should be looking at it. I've been struggling some to make sense of it. There are a couple of issues, but even a few issues can make it very confusing.

You should all be aware that John has posted the schedule at http://poelstra.fedorapeople.org/schedules/f-14/ If you look at f-14-docs-tasks.html it can be very confusing since release notes, announcements and guides tasks are all mixed together. The report, f-14-docs-tree-tasks.html is a lot easier to digest. Until you have your head around that one, the docs combined with translation and releng are totally confusing, so look at the tree tasks first. It is a pity that you don't seem to be able to get a Gantt chart out of

taskjuggler, but if you download the two files from John's "source" directory (f-14.tjp and reports.tji) and open them up in taskjuggler, you can see the dependencies in the source. To do that: 1) Select the tasks tab on the left 2) Highlight the task you wish to examine (note that in general the tasks are folded into higher level tasks) 3) The task will be highlighted in the source on the right, and if there is a dependency, it will say "depends" on the right under the highlighted task name It still isn't super-simple since Docs is only a tiny part of the whole release, and of the hundreds of "external to docs" tasks, there are perhaps a dozen that actually matter to us directly, and they don't always show up within the folded group (e.g. Beta Release Notes), so it isn't always obvious why a particular task has to happen on a particular day without a fair amount of digging. Rudi and I will be getting updates to John, so if you notice anything that seems out of place please let us know. Thanks, --McD

I am going through the schedule, trying to sort out the issues.  And, as in previous releases, there are fewer issues than the release before. The challenge is that most of the issues are non-obvious.  Even when you are pretty intimate with the process, it is hard to catch the disconnects.  I thought if a few more folks would get their eyes on it we would miss fewer things.

I'm willing to do whatever is needed to help produce the best schedule possible for Fedora 14--including creating special reports or having a conference call. Let me know what you need or how you would like to proceed. John P

Yes, TaskJuggler has the illusion of being a GUI scheduling tool like Microsoft Project or GanttProject which it is not. It is better thought of as an IDE. I'm still not following the logic of this thread :) Be bold, ask for exactly what you need to make your work easier! Attached is a gantt chart for the Docs Team and another combining Docs and Translation. Generating this chart is a hack I should probably blog about.

John, I would like to propose the following changes to the Release Notes schedule. Rudi is taking point on the Guides part of the schedule: Add to alpha Validate former beat writers 10 days before "Start Alpha Beat and Feature page Review" Elapsed time 5 days note "Check that beat writers for previous release are willing to contribute to the current release" Recruit new beat writers After "Validate Beat Writers" Elapsed time 5 days note "Identify unmanned beats and recruit contributors to handle those beats" Notify Devel alpha release notes 5 days before "Comb Beats and Feature Pages for Alpha" Elapsed time 0 note "Send notification to devel list that work on alpha release notes is starting and developers wishing to be mentioned should consider commenting in the appropriate beat as well as having feature page complete" Beta changes "Port Wiki to Publican" should extend one day past "Wiki Freeze" "Reminder to development: wiki freeze in 7 days" Should be part of GA release notes, not beta "Build and post release-notes to docs.fedorahosted.org" Change description to: "Build and post beta release notes to docs.fedoraproject.org" Add "Build and post Fedora Technical Notes to docs.fp.o" Same date as "Build and post beta release notes to docs.fedoraproject.org" Change description "Build fed-rel-notes.rpm for Beta Release" to "Build f-r-n.rpm and push to updates-candidate" note "fedora-release-notes.rpm needed for nightly compose" GA Changes add "Update and post Fedora Technical Notes to docs.fp.o" Same date as "Final (GA) Release" Thanks --McD