From Fedora Project Wiki
m (Minor updates)
m (Add questions section)
 
(34 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


== Questions ==
= Release Criteria =
# What is '''success''' for GNOME3 and Fedora 15?
#* There is some talk that GNOME3 might be received in a similar manner as KDE4.0 ... is that good, bad?
# How, or will, the [[Fedora Release Criteria]] be impacted by GNOME3?
# Are Desktop SIG and FESCO in agreement on what is needed and expected from a default desktop experience for Fedora 15?
# Is a multi-release GNOME3 feature roadmap available and maintained?  This might be helpful to assuage any users/maintainers who are unhappy because a feature they relied on is not currently available.
# What kind of Fedora marketing/buzz is planned to raise the profile and get people excited?
# Does [[How to debug Xorg problems]] need to be updated?
# Do we need a [[How to debug GNOME3 problems]] page?


== Documentation Gaps ==
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


# ''Identify'' and document panel applets that are no longer available in Fedora 15 (e.g. Weather and stock applets).
= How to Test =
#* Provide development roadmap/documentation for integrating GNOME2 applets with GNOME3 shell experience
 
# Must document an '''easy''' method for disabling GNOME3 shell and reverting to GNOME2
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.
 
= Open Questions =
# Who is responsible for creating and building EC2 images?
#:
 
= Additional Reading =
* [[Publishing_image_to_EC2]]
* [[Cloud_SIG]]
* [[Cloud_SIG/EC2_Images]]

Latest revision as of 17:19, 9 March 2011

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

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

How to Test

To create an EC2 image, one needs...

  1. an amazon account
  2. the python-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.

Open Questions

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

Additional Reading