[Bug 1258093] [RFE] Cover still-in-progress system wide changes in Alpha release notes

[bugzilla at redhat.com]

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

Pete Travis <me at petetravis.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |me at petetravis.com
         Resolution|---                         |CANTFIX
        Last Closed|                            |2015-08-30 21:17:43



--- Comment #4 from Pete Travis <me at petetravis.com> ---
I was in the room for Joe's talk you mentioned in #1258094, and interjected at
least once to make the distinction between "Release Announcement" and "Release
Notes"; as much as I could without derailing his talk.  They are two discrete
works, each with a different target audience and scope.

To address your point directly, the currently shipped version of the Fedora
Release Notes, available in the fedora-release-notes package from the F23
repos, does discuss contributing to both relnotes content and pre-release QA. 
These release notes don't discuss any release-specific features, at all.

I agree with your points in general.  It would be nice if documentation kept in
sync with development, and users could easily find all the info they're
interested in, and guidance to info on work in progress.  There's room for
discussion and opportunities for contribution, whether under the
Marketing/Magazine tent or at the Docs beat writing desk.  You're welcome
participate in discussions of improving processes, and welcome to participate
in content development, but that conversation doesn't make sense in the context
of a bug report.  

Please mail docs at lists.fedoraproject.org or marketing at lists.fedoraproject.org,
depending on which area you'd like to help improve.  In either case, you'll
probably find that instead of a considered omission, the amount of content
available corresponds with the amount of volunteer time available, and be
invited to directly improve the areas of your concern.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.