Intent to start ARC investigation git-forge replacement
Hello, Fedora community, Following on from the Fedora Council's decision to investigate Forgejo and GitLab as potential replacements[1], the Community Platform Engineering team will start an ARC[2] investigation to compare proposed alternatives for current pagure use cases. The council has defined some broad requirements for the team to consider during this investigation. But we would like inputs from all gitforge user groups in our community. So, if you have a specific use case or workflow, share it with us in the form of a user story in this ticket[6], or consider joining the ARC team for this investigation. High-level overview of investigation requirements by the council: 1. Suitability for dist-git and src.fedoraproject.org replacement 2. Suitability for replacement of Bugzilla for packaging issues and review process 3. Suitability for replacement of Pagure and Bugzilla for release issues (change process, blocker bugs, etc) * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process 4. Suitability for replacement of Pagure for SIG and Team ticket tracking (e.g. FESCo tracker) 5. Cost of hosting and maintenance (hardware + time and resources from CPE and wider infrastructure team) 6. Ease of migration from current Pagure, GitHub, and GitLab 7. Ease of extension and enhancement — can we improve things ourselves to add missing features/features that are cool and useful like CI integration? 8. New features like Asciidoc support, Online editor, and others to make things easier for the Fedora teams and their workflows. 9. Estimate Future risk for Fedora project and Infrastructure team 1. Long-term project vision 2. Platform SMEs in the Fedora Infrastructure team and the wider community These requirements do not represent feature sets, but rather a high-level overview of our current use cases. CPE has already done some initial mapping of how our current applications interact with distgit[3] and if we have missed anything, please let folks know in a thread on discussions.fp.o[4]. The aim of this investigation will not be to pick one solution or the other, but instead, focus on providing the Fedora Council and decision makers[5] with an extensive comparison of the two. For discussion about the purpose of this investigation please use the discussions.fp.o thread[7] The ARC investigation will commence in early May. [1] - https://communityblog.fedoraproject.org/2024-git-forge-evaluation/ [2] - https://fedora-arc.readthedocs.io/en/latest/index.html [3] - https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html#interactions [4] - https://discussion.fedoraproject.org/t/dist-git-decoupling-investigation/93644/10 [5] - https://pagure.io/Fedora-Council/tickets/issue/488 [6] - https://pagure.io/fedora-infra/arc/issue/164 [7] - https://discussion.fedoraproject.org/t/arc-git-forge-investigation/114018 Tomas Hrcka Cat herder at Community Platform Engineering team fas: humaton libera.CHAT: jednorozec matrix: @humaton:fedora.im -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 37 is EOL
Hello all, Fedora Linux 37 has gone end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will be stopped as well. Fedora Linux 38 will continue to receive updates until approximately one month after the release of Fedora Linux 40. The maintenance schedule of Fedora Linux releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions[2] on how to upgrade from a previous release of Fedora Linux to a version receiving updates. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] - https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3] - https://pagure.io/releng -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 End Of Life in one week
Hello all, Fedora Linux 37 will go end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will also be stopped. Please ensure your builds will land in stable[3] updates in Bodhi before the EOL date. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Fedora Release Engineering [1] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3]https://bodhi.fedoraproject.org/updates/?releases=F37=stable -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec @humaton:fedora.im -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Final Freeze
Hi all, Today, 2023-10-03, is an important day on the Fedora Linux 39 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages that fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository. Pending updates will be pushed before the final release as zero day updates. Regards, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/39/final/buglist -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Beta Released
Fedora Linux 39 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora Linux 39 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 39 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 39 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 39 Beta CoreOS: https://fedoraproject.org/coreos/download/ * Get Fedora Linux 39 Beta Cloud: https://fedoraproject.org/cloud/download Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 39 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 39 Beta Labs: https://labs.fedoraproject.org/prerelease For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-39-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka Fedora Release Engineering -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Bodhi updates-testing activation & Beta freeze
Hi all, Today's an important day on the Fedora Linux 39 schedule [1], with several significant cut-offs. First of all, today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora Linux 39 packages must be submitted to updates-testing and pass the relevant requirements [3] before they will be marked as 'stable' and moved to the Fedora Repository. Today is also the Beta freeze [4]. This means that only packages which fix accepted blocker or freeze exception bugs [5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze [7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora Linux 39. Finally, today is the 'completion deadline' Change Checkpoint [8], meaning that Fedora Linux 39 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching - happening in 2hrs
Hi All, Fedora Linux 39 is going to be branched in the upcoming hours as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will reenable builds in koji with notification to this list. Tomas Hrcka Fedora Release Engineering @humaton:fedora.im 1 - https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching
Hi All, Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 UTC as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will re enable builds in koji. 1 - https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 Mass Rebuild started
Hi all, Per the Fedora Linux 39 schedule [1] we have started a mass rebuild on 2023-07-19 for Fedora 39. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (39-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/39-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/39-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list [2] or filing an issue in pagure [3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 final freeze
Hi all, Today, 2023-04-04, is an important day on the Fedora Linux 38 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before the final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 Beta Released
Fedora Linux 38 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 38 Beta, the next step towards our planned Fedora Linux 38 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora Linux 38 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 38 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 38 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 38 Beta CoreOS: https://getfedora.org/coreos/download/ * Get Fedora Linux 38 Beta Cloud: https://getfedora.org/cloud/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 38 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 38 Beta Labs: https://labs.fedoraproject.org/prerelease ## Beta Release Highlights - GNOME 44 - Enabling third-party repositories now enables an unfiltered view of applications on Flathub - Ruby 3.2, gcc 13, LLVM 16, Golang 1.20, PHP 8.2 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-38-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room. Regards, Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 branched
Hi All, Fedora Linux 38 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f39 has been completely isolated from previous releases, so this means that anything you do for f38 you also have to do in the rawhide branch and do a build there. There will be a Fedora Linux 38 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once complete. Bodhi is currently enabled in the f38 branch like it is for rawhide, with automatic update creation. At the hit Beta change freeze point in the Fedora Linux 38 schedule[1] updates-testing will be enabled and manual bodhi updates will be required as in all stable releases. Two things to remember: 1. The modules will be built for a new platform:f39 2. F38/branched release is frozen right now until we get a successful compose, expect that your f38 builds won't be available immediately. Thanks for understanding. Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass branching postpone for 1 day
Hello, the mass branching of Fedora Linux 38 was planned to happen on 2023-02-07. Due to traveling from FOSDEM and the re-signing of rawhide with a new key we will postpone the branching to 2023-02-08. Sorry for the inconvenience Tomas Hrcka Fedora release engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild is finished
Hi all, Per the Fedora Linux 38 schedule[1] we started a mass rebuild for Fedora Linux 38 on 1. 18, 2023. We did a mass rebuild for Fedora 38 for: https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer https://fedoraproject.org/wiki/Changes/GNUToolchainF38 As per the maintainer's request[4] we have skipped all Haskell packages from this rebuild. The mass rebuild was done in a side tag (f38-rebuild) and moved over to f38. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html 20996 builds have been tagged into f38, there are currently 840 failed builds that need to be addressed by the package maintainers. FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on libera.chat, by dropping an email to our list[2], joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure[3] Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ [4] https://pagure.io/releng/issue/11217 ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild started
Hi all, Per the Fedora f38 schedule[1] we have started a mass rebuild on 2022-01-18 for Fedora f38. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (f38-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list[2] or filing an issue in pagure[3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 is End of Life
Hello all, As of the 13th of December 2022, Fedora 35 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 End Of Life in one day
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 End Of Life in one week
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora N being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 37. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
** s390x builders Outage **
There is an ongoing BOS power outage impacting s390x builders. Reason for outage: Power outage in the DC -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 Bodhi updates-testing activation and Beta Freeze
Hi all, Today's an important day on the Fedora 37 schedule[1], with several significant cut-offs. First of all, today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 37 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 37. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 37 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy -- Tomas Hrcka fas: humaton Libera.chat: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 34 is EOL
Hello all, As of the 7th of June 2022, Fedora 34 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 34. All the updates that are currently in testing won't get pushed to stable. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Tomas Hrcka [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 is going EOL in one day.
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 is going EOL in one week
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 is going EOL in 20 days
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Regards, Fedora Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 Beta Release Announcement
Fedora Linux 36 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 36 Beta, the next step towards our planned Fedora 36 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 36 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 36 Beta Server: https://getfedora.org/server/download/ * Get Fedora 36 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 36 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 36 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 36 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * Fedora 36 Workstation Beta includes GNOME 42 * Update of programming languages and libraries: LXQt 1.0, Golang 1.18, Ruby 3.1 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-36-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 36 schedule[1], with several significant cut-offs. First of all, today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 36 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 36. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 36 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Tomáš Hrčka [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 Mass Branching
Hi All, Fedora 36 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f36 has been completely isolated from previous releases, so this means that anything you do for f36 you also have to do in the rawhide branch and do a build there. There will be a Fedora 36 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 36, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 36 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f37 2. The signing of RPMs is not done yet with the new f37 key. 3. F36/branched release is frozen right now until we get a successful compose, expect that your f36 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.CHAT: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 35 schedule[1], with several significant cut-offs. First of all, today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 35 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 35. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 35 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Tomas Hrcka [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.Chat: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F35 mass rebuild is finished
Hi all, Per the Fedora 35 schedule[1] we started a mass rebuild for Fedora 35 on Jul 21st, 2021. We did a mass rebuild for Fedora 35 for: https://fedoraproject.org/wiki/Changes/Autoconf_271 https://fedoraproject.org/wiki/Changes/RPM-4.17 https://fedoraproject.org/wiki/Changes/IBus_1.5.25 https://fedoraproject.org/wiki/Changes/F35Boost176 https://fedoraproject.org/wiki/Changes/F35MingwEnvToolchainUpdate https://fedoraproject.org/wiki/Changes/LTOBuildImprovements https://fedoraproject.org/wiki/Changes/golang1.17 https://fedoraproject.org/wiki/Changes/LLVM-13 The mass rebuild was done in a side tag (f35-rebuild) and moved over to f35. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html 21151 builds have been tagged into f35, there is currently 772 failed builds that need to be addressed by the package maintainers. FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on libera.chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton libera.chat: jednorozec [1] <http://goog_1896774115> https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Mass Rebuild update
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Mass Rebuild
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html> Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html> FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Bodhi Activation point
Hi all, Today's an important day on the Fedora 33 schedule[1], with several significant cut-offs. First of all, today is the Bodhi activation point [2]. That means that from now on all Fedora 33 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 33 Changes must now be code complete, meaning all the code required to enable the new change is finished. The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline'. Finally, today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 33. Tomas Hrcka jednorozec on FreeNode #fedora-releng #fedora-devel #fedora-cs [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org