Lector de Feeds

‎Freeze push request: Freeze move

← Older revision Revision as of 00:38, 24 January 2026 Line 9: Line 9:  == Freeze push request == == Freeze push request ==    −If a developer feels the benefits of having a new version during a freeze overcomes the risks, he/she can send a request including "freeze push" in the subject to the dev@ list including a rationale. One of the [https://people.mageia.org/g/mga-release_managers.html release managers] will evaluate the request and if it seems valid, will perform the push.+If a developer feels the benefits of having a new version during a freeze overcomes the risks, he/she can send a request including "Freeze push" (or "Freeze move", as appropriate) in the subject to the dev@ list including a rationale. One of the [https://people.mageia.org/g/mga-release_managers.html release managers] will evaluate the request and if it seems valid, will perform the push.     The release manager has to issue : <code>mgarepo submit pkg</code> to have it built on our infrastructure. The release manager has to issue : <code>mgarepo submit pkg</code> to have it built on our infrastructure.    −If the packager already built the package in ''updates_testing'' (since that media is still open for building during a freeze), then the release manager must move it to ''release'' rather than rebuilding it there using the appropriate procedure in [[SOP Moving RPMs]].+If the packager has already built the package in ''updates_testing'' (since that media is still open for building during a version freeze), then the release manager must move it to ''release'' rather than rebuilding it there using the appropriate procedure in [[SOP Moving RPMs]].     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf