1
0
Fork 0
forked from releng/tooling
Fedora Release Engineering Scripts
  • Python 86%
  • Shell 12.1%
  • Jinja 1%
  • HTML 0.7%
  • Dockerfile 0.2%
Find a file
Adam Williamson f6a2e8e744 stage_release.sh: correct instructions, allow omitting unused arg
The $STAGE argument has been unused since @kevin split the script
up and fixed some problems in it. Just removing it could cause
problems if people use old invocations fron history or something,
though, so let's allow either passing it or not passing it and
print a warning if it's passed.

Also, update the comment on how the script should be run to
account for the changes to the repository layout and the script's
name.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2026-03-09 08:38:06 -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 Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
misc Migration to Forgejo: releng/tooling Pt 1 2025-10-10 12:59:13 +05:30
packages Remove fedscm_admin bits 2026-01-14 16:51:56 +00:00
quality-assurance critpath.py: output Rawhide data under both 'rawhide' and 'fXX' 2026-02-06 20:59:34 +00:00
release-process stage_release.sh: correct instructions, allow omitting unused arg 2026-03-09 08:38:06 -07:00
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