From Fedora Project Wiki
Page title matches
- == EPEL policy == ...[[Updates_Policy#All_other_updates]], says packages must spend one week in updates-testing before being eligible for release to stable. ...1 KB (215 words) - 18:38, 16 May 2013
- 74 bytes (9 words) - 12:50, 3 February 2021
- #REDIRECT [[Updates Policy]] ...28 bytes (3 words) - 22:16, 28 September 2010
- #REDIRECT [[Talk:Updates Policy]] ...33 bytes (4 words) - 22:16, 28 September 2010
- = Urgent Updates Policy = ...d to this repo are signed and added, then removed a week after the regular updates are pushed to stable. ...2 KB (338 words) - 21:38, 27 August 2015
- {{lang|en|ja|page=Updates Policy}} ...34 bytes (6 words) - 00:12, 2 April 2019
- .... Refer to [[Package update HOWTO]] for the technical steps on pushing the updates. The [[Fedora Release Life Cycle]] provides a more detailed overview of the ...ろんなブランチを使っているFedoraユーザにプッシュすべきかを述べるように心がけています。Fedora委員会からの[[Stable release updates vision]] には、より高レベルの議論や哲学が含まれておりますが、このドキュメントはより実践的な入門書です。更新をプッシュするための技術的な手順は ...57 KB (4,247 words) - 07:56, 3 April 2019
- = EPEL Updates Policy = ...guidelines, refer to the [[EPEL/GuidelinesAndPolicies|EPEL Guidelines and Policy]] page. ...2 KB (398 words) - 20:02, 6 January 2022
- Main points of the policy * Updates should become more conservative as releases pass certain milestones ...16 KB (2,608 words) - 17:06, 7 October 2021
- #REDIRECT [[Updates Policy]] ...28 bytes (3 words) - 09:58, 24 March 2019
- #REDIRECT [[Talk:/Updates Policy]] ...34 bytes (4 words) - 22:15, 28 September 2010
- #REDIRECT [[EPEL Updates Policy]] ...33 bytes (4 words) - 19:27, 19 March 2011
- This is a unordered list of ideas to change/improve the updates process as put forth by many people in the fedora devel and test lists. ...k to before we had any updates criteria. (nuclear option, drop all updates policy). ...3 KB (553 words) - 22:13, 22 March 2011
Page text matches
- = Diagrams for update policy suggestions = [[Image:updates-across-repos-duffy.png | 700px]] ...525 bytes (54 words) - 03:34, 1 September 2010
- #REDIRECT [[Updates Policy]] ...28 bytes (3 words) - 09:58, 24 March 2019
- = News Beat: Updates and Advisories = == Updates and Advisories == ...1 KB (222 words) - 16:45, 3 June 2008
- {{lang|en|ja|page=Updates Policy}} ...34 bytes (6 words) - 00:12, 2 April 2019
- = News Beat: Security Advisories and Package Updates = == Security Advisories and Package Updates == ...1 KB (214 words) - 14:42, 3 June 2008
- This proposal was sent by JesseKeating regarding EOL policy for FedoraExtras: maintainers will be allowed to issue updates to existing packages, but ...2 KB (251 words) - 16:35, 24 May 2008
- This page has been rendered irrelevant by updates to the bundling policy. The previous content is of course available in the page history. ...139 bytes (23 words) - 18:25, 8 October 2015
- === Update policy === Paul: Jesse Keating provided a draft policy for what updates should be done. Board will take this into consideration, if necessary, in ...2 KB (303 words) - 18:00, 11 March 2010
- == EPEL policy == ...[[Updates_Policy#All_other_updates]], says packages must spend one week in updates-testing before being eligible for release to stable. ...1 KB (215 words) - 18:38, 16 May 2013
- ...during the Alpha-Beta time-frame to update their spins, or come up with a policy/guideline for the maintainers to hold on to. === Updates to kickstarts are submitted... where? === ...3 KB (404 words) - 17:55, 10 June 2008
- The "no major updates to stable releases" policy would make life very uncomfortable for certain applications (both maintaine ...d help on how to improve. For everything else, additional encouragement of updates-testing as well as integration between bodhi and packagekit to provide feed ...3 KB (504 words) - 12:04, 29 October 2009
- ...ar repository of packages.</ref> from the [[Repositories#updates-testing|''updates-testing'']] repository to the ''stable'' [[Repositories#fedora|''fedora'']] ...itory. Packages can still be submitted to [[Repositories#updates-testing|''updates-testing'']] in the usual manner, and other releases are not affected at all ...5 KB (767 words) - 00:13, 12 October 2017
- = EPEL Updates Policy = ...guidelines, refer to the [[EPEL/GuidelinesAndPolicies|EPEL Guidelines and Policy]] page. ...2 KB (398 words) - 20:02, 6 January 2022
- ...ar repository of packages.</ref> from the [[Repositories#updates-testing|''updates-testing'']] repository to the ''stable'' [[Repositories#fedora|''fedora'']] ...itory. Packages can still be submitted to [[Repositories#updates-testing|''updates-testing'']] in the usual manner, and other releases are not affected at all ...5 KB (771 words) - 21:50, 1 August 2017
- = Urgent Updates Policy = ...d to this repo are signed and added, then removed a week after the regular updates are pushed to stable. ...2 KB (338 words) - 21:38, 27 August 2015
- 1. updates-testing a. What's the policy for moving from updates-testing to updates? ...5 KB (862 words) - 16:31, 24 May 2008
- * 2011 team travel policy proposal * Updates from Karsten, Harish, and Rahul ...534 bytes (72 words) - 05:09, 15 January 2011
- ...iscussion|Don't forget to check [[User talk:Kparal/Proposal:Package update policy|discussion]] page.}} ...ndling package updates. It specifies when, where and which kind of package updates may occur. ...6 KB (817 words) - 20:06, 9 March 2010
- ...ndling package updates. It specifies when, where and which kind of package updates may occur. * This policy concerns only [[Releases/#Current_Supported_Releases|currently supported Fe ...7 KB (1,015 words) - 15:49, 16 March 2010
- This document summarizes test plans and policies used for package updates in various Linux distributions. It is used for a quick overview and compari ...oftware freedom, etc). Available repositories are 'fedora', 'updates' and 'updates-testing'. ...10 KB (1,382 words) - 06:01, 2 March 2010