Bug 173777
| Summary: | package changes section is a bit silly | ||
|---|---|---|---|
| Product: | [Retired] Fedora Documentation | Reporter: | Jeremy Katz <katzj> |
| Component: | release-notes | Assignee: | Release Notes Tracker <relnotes> |
| Status: | CLOSED NOTABUG | QA Contact: | Karsten Wade <kwade> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | devel | CC: | kwade, sundaram |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-01-25 20:45:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 151189, 168083 | ||
|
Description
Jeremy Katz
2005-11-20 23:20:30 UTC
I've commented out this section in the CVS version, so it won't appear in the build. The info there was outdated (21st September 2005). Added Rahul to the CC list for him to comment, as the Package section of the Release Notes is his. I didnt intend to keep it that way. Just didnt realise the docs freeze time and couldnt polish it up in time for this test release. Next one should be much better. Would be helpful if people communicate better when the release is postponed so that we can time the docs freeze appropriately and announce that. What is really more than a bit silly is even those who are actively in the project not being aware of the release schedule much less the community in general. No announcements of changes in the release schedule were done .The release schedule page still hasnt been updated and yes we shipped crappy release notes on the ISO images. I'm closing this as NOTABUG because we have determined that it is not silly to have a section listing package changes. People often want to know what the status is on a favorite package. We need to automate a process of documenting what those chages are. Otherwise, we are always answering the same questions over again. This seems like it would be a good Infrastructure project, so I've opened bug #178968 as an RFE. |