Difference between revisions of "Release Notes"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= Release Notes = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == <!-- Description should be no longer than a p…')
 
Line 3: Line 3:
  
 
== Project Description ==
 
== Project Description ==
 +
Fedora usually contains three packages that cannot be redistributed with derived (remixed) versions:
  
 +
fedora-logos
 +
fedora-release
 +
fedora-release-notes
 +
 +
Dummy versions of these packages are available, substituting generic- for fedora- (i.e., generic-logos, generic-release, and generic-release-notes).
 +
 +
The fedora-release package has been replaced by the raspberrypi-fedora-remix-release package.
 +
 +
This project involves creating a replacement for the other two packages:
 +
 +
raspberrypi-logos -- This package will contain replacements for the Fedora logos, including the Raspberry Pi logo (and possibly the Fedora secondary mark) where appropriate. It would probably also be a good idea to produce a raspberrypi-backgrounds package with Raspberry Pi-branded wallpaper.
 +
 +
raspberrypi-fedora-remix-release-notes -- This package will contain documentation on the Remix, including notes on how to install it on an SD card, trademarks, use of the GPIO controls, etc.
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
 
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
  
 
== Project Leader(s) ==
 
== Project Leader(s) ==
 
+
Christopher Choo
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
 
<!-- Name(s) of primary people working on the project.  If you want to join a project as leader, discuss with other leaders first.  Include links to personal pages within wiki and to blog sites. -->
  
Line 17: Line 31:
  
 
== Project Details ==
 
== Project Details ==
 +
This part of the project is basically the release notes that are being supplied for the Raspberry Pi Fedora Remix, this includes some how-to documents and notes about what this project is about and any details regarding the remix OS project.
  
 
<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->
 
<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->
Line 29: Line 44:
 
Goals for each release and plans for reaching those goals:
 
Goals for each release and plans for reaching those goals:
 
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
 
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1
+
* 0.1 Read up on how Fedora or other Distributions release notes are structured, figure out what needs to be in the release notes, rough mock up of release notes.
* 0.2
+
* 0.2 Have a semi finished set of release notes and test package, finalize included notes.
* 0.3
+
* 0.3 Have a finished release notes in package.
  
 
== Communication ==
 
== Communication ==
Line 51: Line 66:
  
 
==== Seneca Particpants ====
 
==== Seneca Particpants ====
 +
Christopher Choo
  
 
==== Non-Seneca Participants ====
 
==== Non-Seneca Participants ====

Revision as of 21:47, 8 February 2012

Release Notes

Project Description

Fedora usually contains three packages that cannot be redistributed with derived (remixed) versions:

fedora-logos fedora-release fedora-release-notes

Dummy versions of these packages are available, substituting generic- for fedora- (i.e., generic-logos, generic-release, and generic-release-notes).

The fedora-release package has been replaced by the raspberrypi-fedora-remix-release package.

This project involves creating a replacement for the other two packages:

raspberrypi-logos -- This package will contain replacements for the Fedora logos, including the Raspberry Pi logo (and possibly the Fedora secondary mark) where appropriate. It would probably also be a good idea to produce a raspberrypi-backgrounds package with Raspberry Pi-branded wallpaper.

raspberrypi-fedora-remix-release-notes -- This package will contain documentation on the Remix, including notes on how to install it on an SD card, trademarks, use of the GPIO controls, etc.

Project Leader(s)

Christopher Choo

Project Contributor(s)

Project Details

This part of the project is basically the release notes that are being supplied for the Raspberry Pi Fedora Remix, this includes some how-to documents and notes about what this project is about and any details regarding the remix OS project.


Project Plan

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:

Goals for each release and plans for reaching those goals:

  • 0.1 Read up on how Fedora or other Distributions release notes are structured, figure out what needs to be in the release notes, rough mock up of release notes.
  • 0.2 Have a semi finished set of release notes and test package, finalize included notes.
  • 0.3 Have a finished release notes in package.

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Seneca Particpants

Christopher Choo

Non-Seneca Participants

Planets

Project News