Migration to the new forge

Resource	New Location
Repository	https://forge.fedoraproject.org/releng/tooling
Issue Tracker	https://forge.fedoraproject.org/releng/tickets
Documentation	https://docs.fedoraproject.org/en-US/infra/release_guide/

Reviewers

No reviewers

Labels

Clear labels

after freeze

automation

backlog

Tasks that will take longer then ~4 hours to do

blocked

change-ack

Changes that have releng work and are accepted

change-nak

Changes that have releng work and have been rejected

change-noreleng

Changes that do not have any releng work

changes

Closed As

Can't Fix

Closed with the reason of Can't Fix

Closed As

Duplicate

Closed with the reason of Duplicate

Closed As

Fixed

Closed with the reason of Fixed

Closed As

Fixed with Explanation

Closed with the reason of Fixed with Explanation

Closed As

Get back later

Closed with the reason of Get back later

Closed As

Grooming

Closed with the reason of Grooming

Closed As

Insufficient data

Closed with the reason of Insufficient data

Closed As

Invalid

Closed with the reason of Invalid

Closed As

It's all good

Closed with the reason of It's all good

Closed As

taiga

Closed with the reason of taiga

Closed As

upstream

Closed with the reason of upstream

day-to-day

These are small, self-contained tasks that are part of normal operations but are async from sprint planning.

New artifact for fedora release

Releng Sprint 1 Tracker

sprint-2

Sprint 2

sprint-3

Releng Sprint 3 Tracker

sprint-4

RelEng Spring 4 Tracker

sprint-5

RelEng Sprint Tracker 5 (Nov 18 - Dec 02)

Needs to go through refinement

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

points

02

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

points

03

Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

points

05

A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

points

08

Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

points

13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

Priority

High

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

Priority

Low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

Priority

Medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

Sprint Status

Blocked

Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

Sprint Status

Done

Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

Sprint Status

In Progress

Work items currently being worked on by a team member. Active development, research, or implementation is happening.

Sprint Status

Review

Work items that are complete but need review, testing, or approval before being marked as done.

Sprint Status

To Do

Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

Work Item

Bug

Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

Work Item

Epic

Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

Work Item

Spike

Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

Work Item

Task

Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

Work Item

User Story

User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels

Fixed with Explanation

Projects

No project

Assignees

No assignees

Notifications

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets!13094

Rows
Columns

Migration to the new forge #13094