[Bug 1021342] New: Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Bug ID: 1021342
           Summary: Aggregation of corrections for F20 Release Notes
           Product: Fedora Documentation
           Version: devel
         Component: release-notes
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]

There are surely some typographical corrections and such that need to be made
to the Release Notes. It would make things easier to track them in a single
bug, so please report problems found here.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Pete Travis  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Pete Travis  ---
from tiansworld via trans:
In architecture section,
"ARM in Fedora is all grown up! With the release of Fedora 20 are is considered
a primary architecture meaning that it receives the same amount of attention
that the x86 and x86-64 releases get..."
I think "are" before is, should be arm. It's a typo.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Leslie Satenstein  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Leslie Satenstein  ---
What is the Beta Release?

The beta release is the last important milestone before the release of Fedora
20. A Beta release is code-complete and bears a very strong resemblance to the
third and final release. Only critical bug fixes will be pushed as updates up
to the general release of Fedora 20. The final release of Fedora 20 is expected
in early December.

If you do not as yet have a copy, here is where you go to fetch one.

=======
If I click on here, I do not get the final release of Fedora 20 I get a list of
candidates.

Revise to
======
The beta release is the last important milestone before the release of Fedora
20. A Beta release is code-complete and bears a very strong resemblance to the
third and final release. Only critical bug fixes will be pushed as updates up
to the general release of Fedora 20. If you do not as yet have a candidate
copy, here is where you go to fetch one.

The final release of Fedora 20 is expected in early December.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #3 from Leslie Satenstein  ---
10 Years of Fedora

The Fedora 20 release coincides nicely with the 10th anniversary of Fedora. The
first Fedora release (then called Fedora Core 1) came out on November 6, 2003. 
Since then, the Fedora Project has become an active and vibrant community that
produces nearly a dozen "spins" (A spin is a specially assembled version of
Fedora. Refer to the Spin topic below ) that are tailor made for desktop users,
hardware design, gaming, musicians, artists, and early classroom environments.

=====
For non Fedora users or first time readers, it is good idea to explain what
constitutes a spin. I would add the sentence to refer to the in the lower
section that explains spins.
======

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #4 from Leslie Satenstein  ---
NetworkManager Improvements

NetworkManager is getting several improvements in Fedora 20 that will be
welcome additions for power users and system administrators. 
Users will now be able to add, edit, delete, activate, and de-activate network
connections via the nmcli command line tool, which will make life much easier
for non-desktop uses of Fedora.

=====
The word now is superflous.I would drop the word.
=====

NetworkManager Improvements

NetworkManager is getting several improvements in Fedora 20 that will be
welcome additions for power users and system administrators. 
Users will be able to add, edit, delete, activate, and de-activate network
connections via the nmcli command line tool, which will make life much easier
for non-desktop uses of Fedora.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #5 from Leslie Satenstein  ---
No Default Sendmail, Syslog
Fedora 20 removes some services that many users find unnecessary, though (of
course) they will remain available as installable packages for users who might
need them. 
The systemd journal now takes the place as the default logging solution, having
been tested and able to manage persistent logging in place of syslog.

=========
Consider
replacing 
now takes the place
with 
assumes
=========
The systemd journal assumes the role as the default logging solution, having
been tested and able to manage persistent logging in place of syslog.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #6 from Leslie Satenstein  ---
OS Installer Support for LVM Thin Provisioning 
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.

=====
revision
Please add lvm  as shown below so that the "This" refers to lvm and not the
“improved snapshot functionality” or do you mean both changes. In that latter
case put These changes will make it possible to.....
=====
 This lvm change will make it possible to configure thin provisioning during OS
installation.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #7 from Leslie Satenstein  ---
VM Snapshot UI with virt-manager

This change will make taking VM snapshots much easier. qemu and libvirt have
all the major pieces in place for performing safe VM snapshots/checkpoints,
however there isn't any simple discoverable UI. This feature will track adding
that UI to virt-manager, and any other virt stack bits that need to be
fixed/improved. This includes adding functionality to libvirt to support
deleting and re-basing to external snapshots.

=====
Is it a change or a new feature? 
I have not had occasion to use virt-manager. As written, the feature is assumed
to have been always present, but is an improvement. Is it a change or a new
feature? 
=======
Regarding the words that follow "This"  My comments follow.

"This change will.... " is ok by my public school grammmar.
"This feature will...." is ok by my public school grammar.
but
"This includes adding...   what is the word to add between "This and includes"?

======

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #8 from Leslie Satenstein  ---
Under Developer Goodies.

A formatting comment only.

Should the paragraphs containing a brief description of Developer Goodies be
indented?  The list falls under the above title.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #9 from Leslie Satenstein  ---
Note on performance 
Fedora development releases use a kernel with extra debug information to help
us understand and resolve issues faster; however, this can have a significant
impact on performance. Refer to the kernel debug strategy for more details. You
can boot with slub_debug=- or use the kernel from nodebug repository to disable
the extra debug info.

======
Replace “with extra” with the word “containing extra”.  The debug information
is not next or beside the kernel, it is within the kernel.
======

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #10 from Leslie Satenstein  ---
 Issues and Details 
Heisenbug Alpha is a testing release. To report issues encountered during
testing, contact the Fedora QA team via the test mailing list or in #fedora-qa
on freenode. 
As testing progresses, common issues are tracked at
https://fedoraproject.org/wiki/Common_F20_bugs 
For tips on reporting a bug effectively, read
http://fedoraproject.org/wiki/How_to_file_a_bug_report .

=====
Ḑon't you mean Heisenburg Beta. We are well past the alpha stage. I would
suggest the amendment below.
====
Heisenbug or Heisenburg

Heisenburg pre-release candidates are for testing functionality prior to the
issuing of the final release.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Eric Christensen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #11 from Eric Christensen  ---
Leslie,
It's great you have all these questions but this is *not* the place to be
discussing them.  You should open separate bugs, with patches, preferably,
against the Release Notes.  This bug is *only* for small, typographical errors
that translators might run into.

Thanks

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #12 from Pete Travis  ---
Leslie:
At a glance, it looks like all of the amendments you are proposing are based on
content in the Alpha Release Announcement. The announcement is *different* from
the release notes; none of these complaints apply. As we discussed on the
mailing list, the announcement is a collaborative effort on a wiki page, not a
published guide with an applicable bugzilla component.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #13 from Leslie Satenstein  ---
Hi Pete and Eric.

I may post in the wrong place but please note well. I clicked on the Pete
Travis email on the day I received it and it had a text which said to go "here"
to post changes. I clicked on the "here" link.  Later I received an email from
Eric (saying it was the wrong place to post. But I clicked on the provided link
and sent to my libreoffice markup document.

I may make things difficult, and appear badly in your eyes, but it is not my
intention. I like professional technical writing, and when I worked in a shop
that specialized in documentation, word count was important, as well as
precision. We had to write for machine (google, or other) translator software.

It was drilled into me to scrutinize the grammar.

I have a 12 hour day, been doing it for years, and therefore, I cannot assist
in the IRC chats, or whatever. I relax by reading the posted messages or
minutes of meetings, and I am grateful to Pete for them.

But what I posted, if you look at the "nit-picking" as some would call it, it
is to make the "foreign reader" who is mentally translating the text, follow.
Slang has a bad habit of creeping in.

As well, it is to point out to the editors, that beyond the verification of the
links and the accuracy, that the presentation is well written is one part, but
when a preceding sentence has two or more subjects, if the next sentence begins
with "this", then the this must be qualified.

If you would like more of my nit-picking, I will work my fingers to the bone if
someone could email me draft texts along with a must complete by date.

I have experience with POs and while they are great for translating individual
sentences, they are against clarity for other languages. I live in French
Quebec, and have a Spanish wife, so a) my French is good enough to catch
errors, but not good enough to be efficient at writing succinctly. Similarly
for Spanish.

Please email me at my address which you have on file. if you do not have it, it
is lsatenstein at yahoo point com .  Sorry to respond to you gentlemen via
bugzilla.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #15 from Pete Travis  ---
(In reply to Pete Travis from comment #1)
> from tiansworld via trans:
> In architecture section,
> "ARM in Fedora is all grown up! With the release of Fedora 20 are is
> considered a primary architecture meaning that it receives the same amount
> of attention that the x86 and x86-64 releases get..."
> I think "are" before is, should be arm. It's a typo.

commit f676cd0eb993d5252caa62bf0bd318b3938cf18d
Author: Jérôme Fenal 
Date:   Tue Oct 22 10:44:06 2013 +0200

Fix typo in ARM

Thanks Jérôme!

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #16 from Pete Travis  ---
(In reply to Yuri Chornoivan from comment #14)
> Created attachment 815265 [details]
> A patch to fix typos
>
> Just a patch to fix three issues with spacing and a period.

Patch applied, thanks Yuri!

https://git.fedorahosted.org/cgit/docs/release-notes.git/commit/?id=74a46cd7...

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

TianShixiong  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |g

--- Comment #17 from TianShixiong  ---
In newly updated Filesystem section, there is a typo.
...devices and populating thier filesystems from a recent backup.

thier should be their.

BTW, I would like to fix it by submitting a patch. But I still don't know how
to do it. So please fix it yourself. ：D

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #18 from Pete Travis  ---
Fixed now, thanks.

I like to use git for quick-and-easy patches. Something like:

$ git clone ssh://git.fedorahosted.org/git/docs/release-notes.git # or pull
$ cd release-notes
$ git branch bz1021342;git checkout bz1021342 # create a disposable branch for
the patch
$ vi en-US/Filesystems.xml #fix the error
$ git commit en-US/Filesystems.xml -m "fixing some idiot's typo" 
$ git format-patch master # one patch file created per commit
$ firefox https://bugzilla.redhat.com/show_bug.cgi?id=1021342 # share your
patch
$ git checkout master; git branch -D bz1021342 # destroy the branch, you're
done with it

Feel free to pop in to #fedora-docs for a more interactive discussion :)

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #19 from TianShixiong  ---
Thanks Pete, the procedure you wrote is very clear. I will try it at next time.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #20 from TianShixiong  ---
commit 21461e19f226066f5e53592d0e0bdfdaf13a7f94
Author: Tiansworld 
Date:   Tue Nov 26 22:36:11 2013 +0800

Fixing a small typo, added a space between ControlPort and the URL

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #21 from Pete Travis  ---
(In reply to TianShixiong from comment #20)
> commit 21461e19f226066f5e53592d0e0bdfdaf13a7f94
> Author: Tiansworld 
> Date:   Tue Nov 26 22:36:11 2013 +0800
> Fixing a small typo, added a space between ControlPort and the URL

Fix applied. You forgot to push/attach your patch, Tian :)

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #22 from TianShixiong  ---
(In reply to Pete Travis from comment #21)
> (In reply to TianShixiong from comment #20)
> > commit 21461e19f226066f5e53592d0e0bdfdaf13a7f94
> > Author: Tiansworld 
> > Date:   Tue Nov 26 22:36:11 2013 +0800
> > Fixing a small typo, added a space between ControlPort and the URL
>
> Fix applied. You forgot to push/attach your patch, Tian :)

Is it ok now? I've deleted the patch branch already.

I thought that I should make a push, but there is no "push" according to your
procedure, so I ignored it. 
Anyway, it's the first time to submit something to a public git, caution should
be taken.

I will find some info on how to attach diff info, which Yuri Chornoivan did in
this bug report.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #23 from Pete Travis  ---
(In reply to TianShixiong from comment #22)
> Is it ok now? I've deleted the patch branch already.
>
> I thought that I should make a push, but there is no "push" according to
> your procedure, so I ignored it. 
> Anyway, it's the first time to submit something to a public git, caution
> should be taken.
>
> I will find some info on how to attach diff info, which Yuri Chornoivan did
> in this bug report.

I found the problem easily enough from your description, so no worries. The
only part you missed was that `git format-patch ...` creates some .patch files
in the working directory that you can then share via email or bz.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #25 from TianShixiong  ---
> I found the problem easily enough from your description, so no worries. The
> only part you missed was that `git format-patch ...` creates some .patch
> files in the working directory that you can then share via email or bz.

I did that, but didn't know it would generate a patch file. Now it's attached.
:)

Do I still need 'git push' after 'checkout'?

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #26 from Pete Travis  ---
(In reply to TianShixiong from comment #25)
> > I found the problem easily enough from your description, so no worries. The
> > only part you missed was that `git format-patch ...` creates some .patch
> > files in the working directory that you can then share via email or bz.
>
> I did that, but didn't know it would generate a patch file. Now it's
> attached. :)
>
> Do I still need 'git push' after 'checkout'?

There's no need to `git push` with this method; whoever accepts the patch can
do that part for you. However, members of the "docs-writers" FAS group (which I
believe you are) can skip the branch-patch sequence, commit directly to the
source repo and `git push` their commit.  Either way is fine, that's up to you.

Whether you commit directly or submit patches, it is a good idea to communicate
with the others working on the guide so the work doesn't overlap, strings can
get repushed to tx, etc.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #27 from TianShixiong  ---
> There's no need to `git push` with this method; whoever accepts the patch
> can do that part for you. However, members of the "docs-writers" FAS group
> (which I believe you are) can skip the branch-patch sequence, commit
> directly to the source repo and `git push` their commit.  Either way is
> fine, that's up to you.
>
> Whether you commit directly or submit patches, it is a good idea to
> communicate with the others working on the guide so the work doesn't
> overlap, strings can get repushed to tx, etc.

Nothing more to say, thank you Pete.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Joshua Allen Holm  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #28 from Joshua Allen Holm  ---
The link to "Fedora 20 Features" in section "1.2. Overview" still points to the
page for Fedora 19's features. In the same section, the link that has the text
"http://fedoraproject.org/wiki/Releases/20/FeatureList" also still points to
Fedora 19's features (The text for the link was changed to 20, but not the link
itself). It looks like FeatureList was superseded by ChangeSet on the wiki, so
I assume the correct link should actually be
http://fedoraproject.org/wiki/Releases/20/ChangeSet but I'm not 100% sure.

In section "1.5.1. Providing Feedback on Fedora Software" the link to "Common
F20 Bugs" points to the common bugs page for Fedora 19.

Section "4.1.2. Developer Assistant" makes mention of "documentation in a
devassist-docs package," which, as far as I can tell, does not exist. (yum list
devassist* turns up nothing but devassistant itself).

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

--- Comment #29 from Pete Travis  ---
Good catch, Joshua! I've corrected those entries.

[Bug 1021342] Aggregation of corrections for F20 Release Notes

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1021342

Pete Travis  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|---                         |CURRENTRELEASE
        Last Closed|                            |2014-01-18 17:29:34

--- Comment #30 from Pete Travis  ---
Changes applied and published, thanks everyone!