Talk:Updates Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(EPEL policy: new section)
 
(One intermediate revision by one user not shown)
Line 8: Line 8:
 
* [[User:Bruno|Bruno:]] Should the "Beta to Release" section be named "Beta to Pre Release"?
 
* [[User:Bruno|Bruno:]] Should the "Beta to Release" section be named "Beta to Pre Release"?
 
** [[User:Kevin|Kevin:]] Yep. Done. thanks.
 
** [[User:Kevin|Kevin:]] Yep. Done. thanks.
 +
 +
== EPEL policy ==
 +
 +
Section 4.3, [[Updates_Policy#All_other_updates]], says packages must spend one week in updates-testing before being eligible for release to stable.
 +
 +
EPEL policy appears to be different, perhaps two weeks instead.  Is this documented somewhere that I'm missing?

Latest revision as of 18:38, 16 May 2013

  • Bruno: "Use a seperate buildsystem tag" should probably have a link to instructions on how one does that.
  • Bruno: In the pre-beta section I'd like to see a stronger recommendation against breakage and soname bumps shortly before alpha, since that tends to break spin builds and we'd like to have good, current ones at the time of the alpha release.
    • Kevin: I re-worded things. See what you think.
      • Bruno: I'd like to see something similar related to the Alpha release somewhere.
  • Bruno: Should the "Beta to Release" section be named "Beta to Pre Release"?

[edit] EPEL policy

Section 4.3, Updates_Policy#All_other_updates, says packages must spend one week in updates-testing before being eligible for release to stable.

EPEL policy appears to be different, perhaps two weeks instead. Is this documented somewhere that I'm missing?