Development

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(fix links. This is just horrendous.)
(Spell it out)
 
(One intermediate revision by one user not shown)
Line 22: Line 22:
 
== Quality Assurance ==
 
== Quality Assurance ==
  
* http://fedoraproject.org/wiki/QA
+
For more information about testing and quality assurance in Fedora, refer to the [[QA]] page.

Latest revision as of 13:50, 27 July 2009

There are many ways to engage in the Fedora community, and software development is just one of them. To support software developers, Fedora provides a full set of robust tools and utilities, and even full integrated environments, suitable for a wide variety of pursuits.

Typically, the code for the projects Fedora ships come from one of two places:

  • Inside the Fedora Project, often at the Fedora Hosted repositories
  • Outside the Fedora Project as part of another upstream community

Contents

[edit] Package Maintainers

Information on maintaining packages in Fedora is described in PackageMaintainers.

[edit] Release Schedule

Fedora release schedule is a non-rigid balance between rapid progress and solid quality. Fedora has a public release schedule, with a new release planned approximately every six months. On occasion releases are slightly delayed to fix critical bugs. This release mechanism gives the project goals for which to strive, while maintaining quality.

[edit] Release Planning

Every release has tracker bugs for blockers, targets and updates. This is managed the Fedora ReleaseEngineering team. You can find more details about development plans for current and future releases at the RoadMap page.

[edit] Quality Assurance

For more information about testing and quality assurance in Fedora, refer to the QA page.