Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=228729
Summary: review of README-Accessibility for F7
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: release-notes
AssignedTo: relnotes(a)fedoraproject.org
ReportedBy: kwade(a)redhat.com
QAContact: kwade(a)redhat.com
We need to be sure to review and update (including copyright details) this file
for F7.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243337
Summary: Package should require yelp for its help
Product: Fedora Core
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: fedora-release-notes
AssignedTo: jkeating(a)redhat.com
ReportedBy: mcepl(a)redhat.com
CC: mcepl@redhat.com,relnotes@fedoraproject.org
This package uses yelp for its help. Therefore, it should require package yelp for its operation.
[Filed by a script; forgive him if he made a mistake for once.]
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=905029
Bug ID: 905029
Summary: No system requirements
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: medium
Priority: unspecified
Reporter: a.gormanly(a)ucl.ac.uk
F18 Release Notes does not provide system requirements.
Previous versions did. The Installation Guide refers users to the Release
Notes for this info.
The Fedora Project Homepage lists the below. At least this much detail should
be in the Release Notes, preferably more.
"Recommended installation requirements
64-bit Intel-compatible PC
1GB memory (RAM)
10GB disk space / storage"
--
You are receiving this mail because:
You are the assignee for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=885808
Bug ID: 885808
Summary: Enterprise/advanced storage types that require
interaction to enable/use will not work via UI in in
F18
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: unspecified
Priority: unspecified
Reporter: johannbg(a)gmail.com
Description of problem:
Enterprise/advanced storage types that require interaction to enable/use will
not work via UI in in F18, but can be used via kickstart. UI is scheduled to
re-appear in F19
https://www.redhat.com/archives/anaconda-devel-list/2012-December/msg00025.…
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the assignee for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=883004
Bug ID: 883004
Summary: oVirt Engine for Fedora 18 doesn't include the GUI
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: unspecified
Priority: unspecified
Reporter: juan.hernandez(a)redhat.com
The release notes for Fedora 18 beta include a section about oVirt engine that
describes the feature as it was originally planned, including the addition of
the GUI applications that were not available in Fedora 17. But during the
development of the feature we had to use the contingency plan and as a result
the GUI applications will not be available in Fedora 18.
I think that the right thing to do is to replace that complete section (2.6.3)
with one short paragraph explaining that oVirt Engine has been upgraded to
version 3.1.0.
--
You are receiving this mail because:
You are the assignee for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=895646
Bug ID: 895646
Summary: F18 release notes refer to invalid timedatectl command
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: unspecified
Priority: unspecified
Reporter: mattdm(a)redhat.com
Section 2.3.2.1 says
To list available timezone run the following command:
timedatectl list-timezone
but in systemd-197 as shipped in F18, there is no list-timezone command. (There
is list-timezones, but it does a different thing.)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=828745
Bug ID: 828745
QA Contact: kwade(a)redhat.com
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com, wb8rcr(a)arrl.net
Assignee: relnotes(a)fedoraproject.org
Summary: f17 release note 3.4.7 title should be "vmpk", not
"vpmk".
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: robinlee.sysu(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: release-notes
Product: Fedora Documentation
Description of problem:
f17 release note 3.4.7 title should be "vmpk", not "vpmk".
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=864939
Bug ID: 864939
Blocks: 151189 (fc-relnotes-traqr)
QA Contact: kwade(a)redhat.com
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com, wb8rcr(a)arrl.net
Assignee: relnotes(a)fedoraproject.org
Summary: Note that systemctl now assumes ".service"
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: mattdm(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: release-notes
Product: Fedora Documentation
Provide details here. Do not change the blocking bug.
Previously, systemd required services to have .service appended in systemctl
commands;
$ sudo systemctl restart myservice
$ Failed to issue method call: Unit name myservice is not valid.
-bash: Failed: command not found
$ sudo systemctl restart myservice.service
[okay]
Starting with F18, if there is no dot suffix, systemctl will assume you meant a
service and just work.
This should go in the release notes, because it's a common end-user complaint
about the systemctl user interface.
--
You are receiving this mail because:
You are the assignee for the bug.