From Fedora Project Wiki

No edit summary
No edit summary
Line 22: Line 22:


* Lower Process Capabilities  
* Lower Process Capabilities  
* Contact KDE SIG and gather important changes. Phonon has changed to gstreamer backend in Alpha release and was not mentioned. So call it out in the Beta release.


Additional sources:
Additional sources:
Line 32: Line 34:


* Read Planet Fedora and reference developer blogs when important changes are mentioned
* Read Planet Fedora and reference developer blogs when important changes are mentioned
* Consult with QA team and make sure note worth issues are mentioned. If anything needs explicit testing, highlight it


* More details at https://fedoraproject.org/wiki/Releases/12/FeatureList. Read the release notes section of each of the approved feature
* More details at https://fedoraproject.org/wiki/Releases/12/FeatureList. Read the release notes section of each of the approved feature

Revision as of 20:42, 29 August 2009

This is a DRAFT for feedback. Do not rely on any information here.

Beta is not released yet.

Quick notes:

  • Hybrid ISO - earlier revision in Alpha release notes history. Confirm that it works well before adding it here
  • Moblin - Explain in detail with potentially a screencast
  • GNOME Shell - Ogg Screencast possibly with voice over
  • Yum Presto - In GNOME and KDE groups. What about delta rpm generation?
  • Abrt - whats the status?
  • Anaconda MDRaid - Explain in detail
  • Lower Process Capabilities
  • Contact KDE SIG and gather important changes. Phonon has changed to gstreamer backend in Alpha release and was not mentioned. So call it out in the Beta release.

Additional sources:

  • Look at F11 Preview release notes and use it as a template
  • Read rawhide reports in between alpha and beta release for new packages as well as import changes worth noting here
  • Quickly skimp through all threads in fedora-devel and fedora-test list for note worthy changes
  • Read Planet Fedora and reference developer blogs when important changes are mentioned
  • Consult with QA team and make sure note worth issues are mentioned. If anything needs explicit testing, highlight it