[Bug 1021140] New: Role based access control with libvirt

bugzilla at redhat.com bugzilla at redhat.com
Sat Oct 19 19:04:08 UTC 2013


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

            Bug ID: 1021140
           Summary: Role based access control with libvirt
           Product: Fedora Documentation
           Version: devel
         Component: release-notes
          Keywords: Tracking
          Assignee: relnotes at fedoraproject.org
          Reporter: me at petetravis.com
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: crobinso at redhat.com, jreznik at redhat.com,
                    relnotes at fedoraproject.org, wb8rcr at arrl.net,
                    zach at oglesby.co
        Depends On: 998507



+++ This bug was initially created as a clone of Bug #998507 +++

This is a tracking bug for Change: Role based access control with libvirt
For more details, see: http://fedoraproject.org//wiki/Changes/Virt_ACLs

Allow role based access control with libvirt.

--- Additional comment from Cole Robinson on 2013-08-27 11:57:55 EDT ---

Change is complete in F20/Rawhide, setting to MODIFIED.

--- Additional comment from Jaroslav Reznik on 2013-10-11 04:45:31 EDT ---

This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].

All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be 
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/20/Schedule

============================
Tracking bug for inclusion of the Change in the Release Notes.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=998507
[Bug 998507] Role based access control with libvirt
-- 
You are receiving this mail because:
You are the QA Contact for the bug.


More information about the docs-qa mailing list