Hi Petr

I have not read anywhere of the resume=UUID and use of a second swap file.  So, if there is a calculation of diskspace. Did I miss reading about it in the three guides I reviewed in detail?
We do not have to write about debugging the resume= problem, but that a second swap file for resume is needed for "hybernate" and / or "suspend". 


Leslie Satenstein
Montréal Québec, Canada

On Tuesday, October 9, 2018, 11:31:10 a.m. EDT, Petr Bokoc <pbokoc@redhat.com> wrote:

Hi again,

the final release is coming in a few weeks and we still need help
writing release notes. Instructions are below; if you have any
questions, ping me on IRC or ask here on the list. Any contributions are


On 9/5/18 3:28 PM, Petr Bokoc wrote:
> Hi docs!
> It's that time of the half-year again; we're about a month from the
> current planned date for Fedora 29 final release, and it's time to start
> banging out release notes.
> Anyone who wants to contribute should start here:
> https://pagure.io/fedora-docs/release-notes/issues
> 1. Pick one or more issues that have "F29" 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 tell people how to use something.
> 5. Now the workflow diverges based on your permissions and technical skills:
>     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 "f29". 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 "preview.sh"
> 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 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 October 23, giving us about
> a month and a half. Don't count on the release date slipping :).
> Happy writing!
docs mailing list -- docs@lists.fedoraproject.org
To unsubscribe send an email to docs-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org