tickets/README.md

# Fedora Release Engineering - Issue Tracker

Welcome to the Fedora Release Engineering (RelEng) issue tracker!

## 🎯 What is Fedora Release Engineering?

Fedora Release Engineering is the team responsible for creating, building, and delivering official Fedora releases. We manage the infrastructure and processes that transform thousands of packages into cohesive Fedora products.

### Our Responsibilities

**Release Management**
- Create official Fedora releases (Workstation, Server, Cloud, Spins, etc.)
- Manage release schedules and milestones
- Coordinate freeze periods and go/no-go decisions

**Build Infrastructure**
- Administer the Koji build system
- Manage compose generation and distribution
- Handle package signing and repository creation

**Package Lifecycle**
- Process package updates and new submissions
- Manage package retirement and orphan cleanup
- Handle mass rebuilds for toolchain updates

**Quality Assurance**
- Monitor build health and critical path packages
- Track Failure to Build From Source (FTBFS) issues
- Validate upgrade paths and compose integrity

**Process & Policy**
- Set and enforce freeze management policies
- Report progress to FESCo (Fedora Engineering Steering Committee)
- Maintain and develop release engineering tools

## 📋 What This Issue Tracker Is For

This tracker is for reporting issues related to Fedora Release Engineering processes, tools, and infrastructure.

### ✅ Appropriate Issues

**Infrastructure & Tools**
- Koji build system issues
- Compose generation problems
- Repository synchronization failures
- Signing infrastructure issues

**Release Process**
- Release milestone concerns
- Branching issues
- Mass rebuild coordination
- Update push problems

**Package Management**
- Retirement/unretirement requests
- Critical path package questions
- Tag management issues
- Override requests

**Automation & Scripts**
- Release engineering script bugs
- Automation failures
- Tool enhancement requests
- CI/CD pipeline issues

**Documentation**
- Process documentation improvements
- Missing or unclear procedures
- Release guide updates

### ❌ Issues That Belong Elsewhere

**Individual Package Builds**
- File at the package's issue tracker on [Fedora Packages](https://src.fedoraproject.org/)
- For build failures, contact the package maintainer first

**Bodhi Update Problems**
- File at [Bodhi issue tracker](https://github.com/fedora-infra/bodhi/issues)

**Infrastructure (Non-RelEng)**
- General Fedora infrastructure: [Fedora Infrastructure](https://pagure.io/fedora-infrastructure/issues)

**Package Reviews**
- Use [Bugzilla](https://bugzilla.redhat.com/) for package reviews

**General Support Questions**
- Ask on mailing lists: devel@lists.fedoraproject.org
- IRC/Matrix: [#releng:fedoraproject.org](https://app.element.io/#/room/#releng:fedoraproject.org)

## 🚀 How to Use This Tracker

### Before Filing an Issue

1. **Search existing issues** to avoid duplicates
2. **Check documentation**: https://docs.fedoraproject.org/en-US/infra/release_guide/
3. **Verify it's a RelEng issue** (see appropriate issues above)
4. **Gather relevant information** (logs, error messages, reproduction steps)

## 👥 Who We Are

The Release Engineering team consists of:
- Full-time Fedora Release Engineers
- Part-time contributors and proven packagers
- Community volunteers

We work to ensure Fedora releases are:
- **Reliable** - Consistent quality and stability
- **Timely** - On schedule with predictable cadence  
- **Secure** - Properly signed and verified
- **Accessible** - Available through multiple channels

## 📚 Resources

### Documentation
- **Release Guide**: https://docs.fedoraproject.org/en-US/infra/release_guide/
- **Fedora Infrastructure Docs**: https://docs.fedoraproject.org/en-US/infra/

### Code & Tools
- **RelEng Tooling Repository**: https://forge.fedoraproject.org/releng/tooling
- **Scripts & Automation**: Check the tooling repo for current scripts

### Communication Channels

**Issue Tracker** (you are here!)
- https://forge.fedoraproject.org/releng/tickets

**Mailing List**
- devel@lists.fedoraproject.org (general discussion)
- [Subscribe/Archives](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/)

**Chat (IRC/Matrix)**
- Matrix: [#releng:fedoraproject.org](https://app.element.io/#/room/#releng:fedoraproject.org)
- IRC: #releng:fedoraproject.org

## 🤝 Contributing

Want to help improve Fedora Release Engineering?

1. **Participate in discussions** on issues
2. **Submit pull requests** to the [tooling repository](https://forge.fedoraproject.org/releng/tooling)
3. **Improve documentation** with your knowledge
4. **Join RelEng meetings** to stay informed
5. **Report issues** you encounter

Check our [Contributing Guide](https://forge.fedoraproject.org/releng/tooling/src/branch/main/CONTRIBUTING.md) for more details.

## ❓ Frequently Asked Questions

**Q: How do I request a package unretirement?**

A: File an issue here with the package name and justification for unretirement.

**Q: My package build failed in Koji, what do I do?**

A: If it's a package-specific issue, contact the maintainer. If it's a broader infrastructure issue affecting multiple packages, file an issue here.

**Q: How do I request a buildroot override?**

A: Use the [Bodhi web interface](https://bodhi.fedoraproject.org/) for override requests.

**Q: When is the next release?**

A: Check the [Fedora Release Schedule](https://fedoraproject.org/wiki/Releases/Schedule).

**Q: How do I become a Release Engineer?**

A: Start by contributing to RelEng tasks, attending meetings, and getting involved in the community. Contact the team through our communication channels.

## 📅 Release Schedule

Fedora follows a time-based release schedule with releases approximately every 6 months. Each release goes through several phases:

1. **Branching** - New release branch created
2. **Development** - Active development and testing
3. **Freeze Periods** - Various freezes (Change Checkpoint, Beta, Final)
4. **Beta Release** - First public release for testing
5. **Final Release** - Official stable release
6. **Maintenance** - Updates and security fixes

Current and upcoming schedules: https://fedoraproject.org/wiki/Releases/Schedule

## 📞 Emergency Contact

For urgent, release-blocking issues:
1. **File a high-priority issue** here with `[URGENT]` in the title
2. **Notify on IRC/Matrix** in #releng:fedoraproject.org
3. **Email the mailing list** if immediate response needed

---

**Thank you for helping make Fedora releases better!**

The Fedora Release Engineering Team