Fedora Linux has announced the release of Fedora Linux 43 Beta RC 1.1, a crucial step in the development of the forthcoming Fedora 43 version. This beta release is now available for community testing, and active participation is encouraged to ensure thorough validation against a set of predefined criteria. The testing process requires that all priority test cases pass across six specific areas: installation, base, server, cloud, desktop, and security lab configurations.
Key Developments:
- The release of Fedora 43 Candidate Beta-1.1 marks a significant advancement in the Fedora project's timeline.
- Community involvement is crucial; individuals can contribute to testing and validation efforts.
- A detailed test coverage report is accessible online, providing insights for testers.
Release Criteria and Testing:
To successfully meet the Beta release criteria, all priority test cases must be validated in the following categories:
- [Installation](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Installation)
- [Base](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Base)
- [Server](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Server)
- [Cloud](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Cloud)
- [Desktop](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Desktop)
- [Security Lab](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Security_Lab)
Current Blocker and Freeze Exception Bugs:
For updates on current blocker bugs, participants can refer to the [blocker bugs page](https://qa.fedoraproject.org/blockerbugs/current).
Download Fedora 43 Candidate Beta-1.1 Images:
Interested testers can download the beta images from [this link](https://kojipkgs.fedoraproject.org/compose/43/Fedora-43-20250910.0/compose/).
In conclusion, the Fedora community is encouraged to engage actively in the testing phase of Fedora 43 Beta RC 1.1, as this involvement is vital for identifying and resolving potential issues before the final release. As the development process progresses, the community's feedback will play a crucial role in shaping the stability and usability of the final product
Key Developments:
- The release of Fedora 43 Candidate Beta-1.1 marks a significant advancement in the Fedora project's timeline.
- Community involvement is crucial; individuals can contribute to testing and validation efforts.
- A detailed test coverage report is accessible online, providing insights for testers.
Release Criteria and Testing:
To successfully meet the Beta release criteria, all priority test cases must be validated in the following categories:
- [Installation](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Installation)
- [Base](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Base)
- [Server](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Server)
- [Cloud](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Cloud)
- [Desktop](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Desktop)
- [Security Lab](https://fedoraproject.org/wiki/Test_Results:Fedora_43_Beta_1.1_Security_Lab)
Current Blocker and Freeze Exception Bugs:
For updates on current blocker bugs, participants can refer to the [blocker bugs page](https://qa.fedoraproject.org/blockerbugs/current).
Download Fedora 43 Candidate Beta-1.1 Images:
Interested testers can download the beta images from [this link](https://kojipkgs.fedoraproject.org/compose/43/Fedora-43-20250910.0/compose/).
In conclusion, the Fedora community is encouraged to engage actively in the testing phase of Fedora 43 Beta RC 1.1, as this involvement is vital for identifying and resolving potential issues before the final release. As the development process progresses, the community's feedback will play a crucial role in shaping the stability and usability of the final product
Fedora Linux 43 Beta RC 1.1 released
Fedora Linux 43 Beta RC 1.1 is now available for testing, marking a significant milestone in the development process for the upcoming Fedora 43 release. Community members are encouraged to participate in the validation process by testing the release against predefined criteria and providing feedback. To meet the Beta release criteria, all priority test cases for the Beta must pass for each of the six test pages covering installation, base, server, cloud, desktop, and security lab configurations.
