Bug 1583863 - Release Notes Fedora 28
Summary: Release Notes Fedora 28
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: technical-notes
Version: devel
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: John J. McDonough
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-29 23:11 UTC by Leslie Satenstein
Modified: 2019-11-07 15:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 15:30:24 UTC
Embargoed:


Attachments (Terms of Use)
Fedora 28 Release Notes (47.85 KB, application/vnd.oasis.opendocument.text)
2018-05-29 23:11 UTC, Leslie Satenstein
no flags Details

Description Leslie Satenstein 2018-05-29 23:11:21 UTC
Created attachment 1445585 [details]
Fedora 28 Release Notes

Description of problem:

I copy / pasted the Fedora Release Notes from https://docs.fedoraproject.org/

Version-Release number of selected component (if applicable):

Fedora 28

I used LibreOffice writer to edit the guide.

I marked spelling errors, grammar errors, and sentence construction.

I also raised comments about different sections of the release guide. Vague or incorrect information

I would like « anyone » to review the attached document and accept/reject the changes

Zoom to each markup. Use the right mouse button on the error to acknowledge or reject the change I made or error I detected. You may add your own changes too. 

My intention, if my changes to the guide are marked up, is to back post the changes to the asciidoc files, raising a PR (whatever a PR is). 
 
Please email me your approvals/rejects using the same document.
Or respond with your attacement as a new comment

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Feedback confirming my findings

Additional info:

Comment 1 Petr Bokoc 2019-11-07 15:30:24 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


Note You need to log in before you can comment on or make changes to this bug.