This installment of the Heroes of Fedora series will focus on work done on Fedora 24 Final version.
Welcome back to the final installment of Heroes of Fedora 24 – Final edition! The purpose of this post is to recognize the contributors who made a difference in releasing Fedora 24 Final. Below you’ll find stats for Bodhi updates, release-validation tests, and Bugzilla reports. Without further ado, let’s get started!
This installment of the Heroes of Fedora series will focus on work done on Fedora 24 Beta release. Fedora is growing! Let’s check it out…
Let’s get right back into it with the Fedora 24 Beta release statistics regarding Bodhi updates, release-validation tests, and Bugzilla reports. The numbers don’t lie, keeping in favor with the idea that Fedora is growing!
It’s time for another round of Heroes of Fedora! This time, we’re covering Fedora 24 Alpha.
As is usual with the release of a new version of Fedora, it’s time to reflect on the stats revolving around what it took to get the latest-and-greatest out the door. With the recent push of F24, the numbers are in, so without further delay, let’s check ’em out!
Open source is the new trend. When major corporations are moving towards open architecture by using open source tools and even pushing their internal projects into open source, it makes your contributions especially worthy. But before starting with contributing, many people face the same common set of questions. How they can start, how should they introduce themselves in the community, and where they can contribute. To answer these questions, I planned a session on free and open source software (FOSS) and Fedora at the in Delhi, India.
During the planning phase, I got in touch with Sumantro, who is himself an open source enthusiast and contributing to various open source projects including the Fedora Project. With his help, we planned the agenda for the session and gathered the resources to conduct the session. On 12th August, 2016, this session on FOSS and Fedora was conducted to:
A start of a big journey!
Furthering the efforts of some work around building a strong, tight-knit FOSS community around Fedora, I approached a few people from Bhopal, Madhya Pradesh. I figured out the scope to talk about Fedora and Fedora quality assurance (QA). The target audience was bringing more college students from Bhopal into open source and Fedora.
The meeting was short and simple. The audience was well-versed with free and open source software (FOSS) and many of them are presently contributing to various FOSS projects. We started off talking about how contributing to FOSS makes contributors industry-ready. As the cog wheel of time revolved, we shifted to “how people can join” the Fedora Project and start contributing!
Heroes of Fedora 23 bonus content – a quick post on Test Day stats.
I realized that in Heroes of Fedora 23 Alpha I promised statistics on Test Days in the Fedora 23 Final post, but forgot to include them when writing it! The Fedora 24 HoF posts will start up soon, but in the mean time, here are the Fedora 23 Test Day stats as a little bonus!
‘Overall fixed %’ is an approximation of what proportion of the bugs reported as part of Test Day events were ‘fixed’. Calculating it involves some subjective choices that have been discussed on the test@ mailing list before, but it’s a reasonable approximation. These stats are generated by this ‘testdays’ tool.
Events: 6
Tests: 318
Bugs: 29
Testers: 28
Overall fixed %: 56.5217391304
This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.
This is the third and last part of the Getting started with Fedora QA series. In the last post, we talked about how to create your test environment and use Bodhi to test updates and leave feedback. This article will focus on running test cases and how to complete one.
This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.
This is a continuation of the previous post in this series of how to get involved with the Fedora Quality Assurance (QA) team. Make sure you have the Bugzilla, FAS account, and email alias set up before following these steps. You can find more information about how to get those accounts in the earlier post.
There are several different tools and services available to help us test Fedora. This helps us insure the quality of software and stay on target for a stable release. One of the easiest ways to get involved is to run Rawhide, the ever-changing development version of Fedora, or a pre-release version like the Alpha or Beta. While you are able to upgrade your system directly to these versions, sometimes you may want to use a virtual machine (VM) to work in. We’ll cover some of the Fedora-specific tools for quality assurance testing as well as setting up your environment for testing.
For a while now, Fedora Quality Assurance (QA) is busy with building Taskotron core features and didn’t have resources for additions to tasks that Taskotron runs. That changed a few weeks back when we started running task-dockerautotest, task-abicheck and task-rpmgrill tasks in our development environment. Since then, we are happy with the results of those tasks. We deployed them to the production instance last week. Please note that the results of those tasks are informative only. Let’s introduce the tasks briefly.
Many important packages and software are developed for Fedora every day. One of the most important parts of software development is quality assurance, or testing. For important software collections in Fedora, there are sometimes concentrated testing efforts for pulling large groups of people in who might not always help test. Organizing a Fedora Test Day is a great way to help expose your project and bring more testers to trialing a new update before it goes live.
Most of the time, you will be able to test software updates without help. But for larger software or packages crucial to Fedora, having more eyes and hands to poke around is useful and helpful. This post explains and walks you through the process for organizing your own Fedora Test Day and what work goes into it.
Copyright © 2024 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments