Policy for package lifecycle

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Added onlyinclude tags)
(update to match current policy)
Line 9: Line 9:
 
-->
 
-->
  
* When a Fedora Core release reaches maintenance state in its lifecycle (such as Fedora Core 3 when Fedora Core 5 Test 2 was released), the corresponding release of Fedora Extras will also enter a maintenance state.
+
* One month after Fedora version N is released, Fedora release N-2 reaches End-of-life (EOL) (so fedora Fedora 7 was End-of-life one month after Fedora 9 release).
  
* Branches for new packages in CVS are not created for distributions that are in maintenance state. The official package maintainers are also urged to fix their packages for distributions that are in maintenance state.
+
* Branches for new packages in CVS are not allowed for distribution N-2 after the Fedora N release. New builds are no longer allowed for EOL Fedora releases.
  
* When the Fedora Project drops support for a Fedora Core release, the corresponding Fedora Extras is also dropped -- this is End-of-life (EOL).
+
* Bugs of EOL releases are closed automatically.
 
+
* The EOL Policy depends on the creation of a Security Response Team that will lend assistance as needed if the maintainer is unable to fix the package.
+
  
 
<!-- INCLUDEPOLICYFRONTEND
 
<!-- INCLUDEPOLICYFRONTEND
Line 25: Line 23:
 
== More Details ==
 
== More Details ==
  
When a Fedora Core release reaches maintenance state in its lifecycle (such as Fedora Core 3 reached when Fedora Core 5 Test 2 was released), the corresponding release of Fedora Extras will also enter a maintenance state. In this state, maintainers will be allowed to issue updates to existing packages, but maintainers are strongly urged to only issue severe bugfix or security fixes. New software versions should be avoided except when necessary for resolving issues with the the current version.
+
One month after Fedora release N, Fedora N-2 release reaches End-of-life (EOL). This means that no new builds are accepted, and [[BugZappers/HouseKeeping#End_of_Life_.28EOL.29| bugs are not looked at anymore]].
 
+
Branches for new packages in CVS are not created for distributions that are in maintenance state. FESCo can approve exceptions of this rule if there are good reasons for it. The official package maintainers are urged to fix their packages also for distributions that are in maintenance state. They should work hand in hand with the "Security Response Team" in case they don't have access to older
+
distros anymore to test their updates.
+
  
When the Fedora Project drops support for a Fedora Core release, the corresponding Fedora Extras is also dropped -- read this as
+
Branches for new packages in CVS are not created for distributions one month before the EOL, that is when Fedora N is released, branches for Fedora N-2 are not created anymore.
"End-of-life, no new updates,support for that EOL distro will be removed from the Extras buildsys".
+
  
The EOL Policy depends on the creation and a working [http://fedoraproject.org/wiki/Security Security Response Team]  and especially the part of it that "will lend assistance as needed" if the maintainer is unable to fix the package -- if that group does not start working properly until June 15 2006 we'll send out a EOL for Fedora Extras 3 -- means: "Packagers can still update things in cvs and build updates for now, but the official state of Fedora Extras 3 is 'unsupported and End of Life'". In that case we'll try to improve for FE4 and later.
+
FESCo can approve exceptions of these rules if there are good reasons for it.
  
This is the initial policy that was approved by the Steering Committee on 2006-05-04.
+
Bugs for EOL releases should be closed automatically.

Revision as of 15:38, 16 November 2008

Fedora Extras Maintenance Lifecycle Policy

Digest

  • One month after Fedora version N is released, Fedora release N-2 reaches End-of-life (EOL) (so fedora Fedora 7 was End-of-life one month after Fedora 9 release).
  • Branches for new packages in CVS are not allowed for distribution N-2 after the Fedora N release. New builds are no longer allowed for EOL Fedora releases.
  • Bugs of EOL releases are closed automatically.


More Details

One month after Fedora release N, Fedora N-2 release reaches End-of-life (EOL). This means that no new builds are accepted, and bugs are not looked at anymore.

Branches for new packages in CVS are not created for distributions one month before the EOL, that is when Fedora N is released, branches for Fedora N-2 are not created anymore.

FESCo can approve exceptions of these rules if there are good reasons for it.

Bugs for EOL releases should be closed automatically.