Request Page Redesign - Maintenance Action Types
After a while keeping working on the request page redesign, we are glad to come back to you with two new request types: maintenance incident requests and maintenance release requests.
The request redesign is part of the beta program.
We started the redesign of the request workflow in August 2022. Then, in September 2022, we focused on the support of multi-action submit requests. We continued in October 2022 with improvements regarding the Build Results tab and superseded conversations, and we presented build results with a pinch of salt in November 2022. In January 2023, we worked on facilitating the review process. In February 2023 we enhanced the review process with comments on changes. Later, in April 2023, we focused on improving the comments on changes and supporting new types of actions. In June 2023 we worked on maintenance action types. In July 2023 we introduced Set Bugowner action and diff comments for non-beta users. In September 2023 we focused on Build Results Summary Gets Into Shape. Later 2023, in November, we added the Build Status Refresh and Other Insights on Our Request Page. The year 2024 started with Revamping the Request Build Status Page and Introducing the Dark Mode. This time we give you a little update with Build Results Summary Chart Links to Build Results Overview.
What are Maintenance Incident Requests and Maintenance Release Requests?
Maintenance incident requests and maintenance release requests are two different types of OBS requests used in a maintenance update process, typically when a distribution is already frozen and needs to recieve updates. This is explained in detail in the “Maintenance Support” section of the OBS User documentation.
Add Request Actions for Maintenance Incidents
Add Request Actions for Maintenance Releases
How To Give Us Feedback
There are two ways to reach us:
- On GitHub, by opening an issue and / or commenting on an already opened issue.
- On IRC, by talking directly to us. We are in the channel
Please note that we favor GitHub to gather feedback as it allows us to easily keep track of the discussions.