1
0
Fork 0
forked from releng/tooling
Fedora Release Engineering Scripts
  • Python 85.9%
  • Shell 12.2%
  • Jinja 1%
  • HTML 0.7%
  • Dockerfile 0.2%
Find a file
Adam Williamson ec9c972fec Add ccp.py - compose-critical package list generation script
This adds ccp.py - a script for generating the "compose-critical
package list" for a given compose. It's a bit of a WIP but it
does already work and give you a fairly useful list (as a flat
text file for now).

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2026-07-07 16:19:42 -07:00
.forgejo Add codeowners for releng tooling repo 2026-02-09 12:25:29 +05:30
builds Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
infrastructure infrastructure/messaging: correct path to fedora_messaging_logger.py 2026-06-09 13:36:37 -07:00
misc Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
packages packages: read $PAGURE_TOKEN instead of fedscm-admin config 2026-05-19 13:20:34 -05:00
quality-assurance Add ccp.py - compose-critical package list generation script 2026-07-07 16:19:42 -07:00
release-process fix indentation and method declaration 2026-06-11 12:40:05 +05:30
sync Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
utilities Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
.gitignore Add .idea folder to gitignore 2019-02-21 11:26:26 +01:00
CONVENTIONS.md Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
README.md Link directly to new tickets. 2025-12-09 08:59:13 +00:00

Fedora Release Engineering Scripts (New Structure)

This directory contains the reorganized structure for Fedora Release Engineering scripts, designed for better maintainability and clarity.

📁 Directory Structure

🔧 Migration Status

⚠️ This is the new directory structure under development.

Scripts are being migrated from the flat scripts/ directory to this organized structure. See CONVENTIONS.md for naming standards and migration guidelines.

📖 Getting Started

  1. Review CONVENTIONS.md for naming and organization standards
  2. Check individual directory READMEs for specific tool documentation
  3. Use the directory structure to quickly locate relevant scripts