May I offer my opinion as an end-user and the guy who raised the bug? Here it is, even if
you say no.
Other distributions (example Suse13.2 and Mint 17) which I explored, handled situations by
updating the web based release notes. I will verify that their pdf version of release note
follows the web updates.
Anaconda is not buggy, and as I see it, the right place to add the informational message
is to update the release note, which in my view is a working document. There are another
12 months of Fedora21 to support. Release notes should not be cast in stone, unmutable by
release, they are a guide to the person wanting to install Fedora.
I would put a dated paragraph into the release note to explain what might cause the
execution delay. I don't expect to see the Release note for F22, when it is produced
being a copy and paste of the F21 note, with a few revisions. The note is what I would
expect to experience as a Fedora installer.
Do the release notes have to be translated and released simultaneously? I would put a
comment into the translated notes that the most recent notes updates are within the
Mr. Leslie Satenstein
Montréal Québec, Canada
From: Chris Murphy <lists(a)colorremedies.com>
Sent: Wednesday, December 10, 2014 4:25 PM
Subject: re: commonbugs draft text for bug 1170803
I like to get the expected behavior up front, then explain the
ramifications. Maybe it helps people who are just skimming retain the
"To make sure any extN filesystems that might be reused or resized are
healthy, the Fedora installer automatically performs a check on
filesystems it discovers. If this check takes a long time, perhaps because
of large, slow, or damaged filesystems, the installer may..."
The expected behavior is fsck should run only on volumes that are explicitly set to be
resized. Instead, all ext volumes are fsck'd pretty much right away.
Or, are you asking for it to be included in the RNs?
No just http://fedoraproject.org/wiki/Common_F21_bugs
I think is OK?
docs mailing list