I'd like to announce that all versioned docs now have a "f30" branch,
and specifically the F30 Release Notes are ready for your contributions.
Anyone who wants to contribute should start here:
1. Pick one or more issues that have "F30" in the title.
2. Open each issue you picked, and click the Take button on the right to
claim it. (If you claim an issue but later find out you don't have time
to write about it, remove yourself from the issue ASAP so others can see
it's free and take it!)
3. Find some information about the issue. A lot of them have plenty of
info in them already; if not, find out who's responsible for the change,
and talk to them on IRC or via mail. Of course it's always better if you
try to do research before you ask questions.
4. Write a release note about the issue. If you're not sure how exactly
a release note looks, check out some of the previous releases for
inspiration. We don't want any long, overly technical texts, the release
notes are meant to highlight changes, not to tell people how to use
5. Now the workflow diverges based on your permissions and technical
5a. If you know how to use git and asciidoc, we'd appreciate if you
wrote up the release note and sent a pull request against the main repo,
branch "f30". Note that we have a different directory structure for this
release; your contributions should go into one of the files in
"modules/release-notes/pages/". Use the "build.sh" and
scripts in the repository root to preview your changes locally; see the
repository README for specific instructions. If you can't see the
section where you added your contributions at all, make sure it's
included in "modules/release-notes/nav.adoc".
5b. If the above sounds like gibberish to you, it's fine: just add a
comment with your text into the issue, and ping me on IRC/Telegram or
through e-mail; I'll mark it up for you and make sure your contribution
appears in the final document.
If anyone has any questions, go ahead and ask. The current schedule
shows the preferred final release target at April, giving us less than 3
weeks. The release date may slip, but don't count on it.
Also, note that right now, if you build a local preview of any of the
F30 versioned docs, they'll be missing the table of contents. It's a
known issue and should be fixed soon, I just don't have the permissions
so I need to wait for Adam.
Finally, apologies for doing this so late, I've been indisposed for the
last week or so due to some IRL problems.