User:Jlaska/Draft3

From FedoraProject

< User:Jlaska(Difference between revisions)
Jump to: navigation, search
(Updated content)
m (Add questions section)
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{draft}}  
+
{{header|qa}}
 +
{{draft}}
  
General ideas/discussion intended to ensure a successful [[Features/Gnome3|GNOME3]] release in Fedora 15.
+
This page will outline criteria for success for a Fedora AMI release
  
= What is Success? =
+
= Release Criteria =
  
A ''successful'' GNOME3 and Fedora 15 release are defined as:
+
In addition to the existing [[Fedora Release Criteria]], the following criteria apply to EC2 Fedora images.  A <span style="color:green; font-weight:bold;">good</span> AMI '''must'''...
 +
# allow non-root user login
 +
# have SELinux enabled and ''enforcing'' by default
 +
# not contain any package dependency problems
 +
# not include any packages built outside of Fedora infrastructure
  
# runs on a reasonable range of graphics hardware
+
= How to Test =
# offers a graceful fallback for the rest
+
# has working controls for common things like keyboards, monitors, network, sound and power
+
# all desktop applications work and any applications built against gtk3 ...
+
#* don't show status icons (http://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/Compatibility)
+
#* use modal dialogs
+
#* install hi-res icon
+
  
= Open tasks =
+
To ''create'' an EC2 image, one needs...
 +
# an amazon account
 +
# the {{package|python-boto}} libraries installed
 +
# a python script to tell Amazon to build an instance
 +
# the ability to SSH into a machine to run tests, etc.
  
# graceful fallback - code is needed to gracefully handle the following scenarios ...
+
= Open Questions =
#* Insufficient hardware - the system hardware is known to not handle gnome-shell, and fallback mode is recommended
+
# Who is responsible for creating and building EC2 images?
#* shell failure - The shell crashes or fails to start for an unknown reason, a suitable fallback should be offered instead
+
#:
  
{{admon/important|Where's the bug?|Are the above open tasks tracked in upstream bugzilla?}}
+
= Additional Reading =
 
+
* [[Publishing_image_to_EC2]]
= FAQ =
+
* [[Cloud_SIG]]
 
+
* [[Cloud_SIG/EC2_Images]]
== General ==
+
 
+
; When is the upstream decision made as to whether 2.91.x will become 3.0?
+
: ??? (FIXME)
+
 
+
; How is the upstream decision made as to whether 2.91.x will become 3.0?  Is it dependent on blocker bug resolution, or release criteria?
+
: ??? (FIXME)
+
 
+
; If GnomeShell isn't considered ready by upstream, how will Fedora proceed?
+
: ??? (FIXME)
+
:# Fedora 15 slips until GNOME3 is ready
+
:# Fedora 15 ships GNOME3 in fall-back mode only (shell with metacity+panel)
+
:# Fedora 15 ships Fedora 14 GNOME
+
:# <your idea here>
+
 
+
; Where can I find GnomeShell marketting plans for upstream GNOME and Fedora?
+
: ??? (FIXME)
+
 
+
; What testing (GNOME and Fedora) is planned for GnomeShell?
+
: ??? (FIXME)
+
 
+
== Features ==
+
 
+
; What happened to the Fedora 14-vintage GNOME shell favorites sidebar allowing selection+presentation of favorite applications and folders?
+
: ??? (FIXME)
+
 
+
; How should multi-monitor support behave with GnomeShell in Fedora 15?
+
: Currently, GnomeShell just treats any additional monitors as extra space to put windows in but otherwise more or less ignores them.  When you go into overview mode, it only takes effect on one screen, the others are just left blank. There's nothing yet done to integrate the workspace model the Shell encourages with multi-monitor setups.  There's a bug for this, but again, AFAICT no particular commitment to fixing it up before the 3.0 release. (This isn't actually much of a 'regression' compared to GNOME 2, which was similarly lax about doing much with extra screens, but it's the sort of thing people might expect GNOME 3 to have fixed).
+
: ??? (FIXME)
+
 
+
== Workarounds ==
+
 
+
; What is the procedure to manually revert to fallback mode?
+
: ??? (FIXME)
+

Latest revision as of 17:19, 9 March 2011

QA.png


Warning (medium size).png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

This page will outline criteria for success for a Fedora AMI release

Contents

[edit] Release Criteria

In addition to the existing Fedora Release Criteria, the following criteria apply to EC2 Fedora images. A good AMI must...

  1. allow non-root user login
  2. have SELinux enabled and enforcing by default
  3. not contain any package dependency problems
  4. not include any packages built outside of Fedora infrastructure

[edit] How to Test

To create an EC2 image, one needs...

  1. an amazon account
  2. the Package-x-generic-16.pngpython-boto libraries installed
  3. a python script to tell Amazon to build an instance
  4. the ability to SSH into a machine to run tests, etc.

[edit] Open Questions

  1. Who is responsible for creating and building EC2 images?

[edit] Additional Reading