#12227 create EPEL 10.0 release in bodhi
Closed: Fixed 6 months ago by jnsamyak. Opened 6 months ago by carlwgeorge.

  • Describe the issue

I think we're ready to create the EPEL 10.0 release in bodhi in order to continue the EPEL 10 implementation. Based on my planning and research (including #10413), I believe this is the correct command that needs to be run.

bodhi releases create \
    --name "EPEL-10.0" \
    --long-name "Fedora EPEL 10.0" \
    --version 10.0 \
    --branch epel10 \
    --id-prefix FEDORA-EPEL \
    --dist-tag epel10.0 \
    --stable-tag epel10.0 \
    --testing-tag epel10.0-testing \
    --candidate-tag epel10.0-testing-candidate \
    --pending-signing-tag epel10.0-signing-pending \
    --pending-testing-tag epel10.0-testing-pending \
    --pending-stable-tag epel10.0-pending \
    --override-tag epel10.0-override \
    --mail-template fedora_epel_legacy_errata_template \
    --state pending \
    --not-composed-by-bodhi \
    --create-automatic-updates
  • When do you need this? (YYYY/MM/DD)

Ideally by 2024/08/02 (this Friday) so it's ready for the EPEL 10 hackfest at Flock.

  • When is this no longer needed or useful? (YYYY/MM/DD)

RHEL 10 EOL (estimated 2035/05/31).

  • If we cannot complete your request, what is the impact?

Blocks further work on EPEL 10.


I do want to note that I intentionally used the --not-composed-by-bodhi and --create-automatic-updates flags. This is to emulate rawhide during the earliest days of EPEL 10. In the future we'll change these properties to enable the testing repo. If there are questions about this, please feel free to reach out directly to me in chat.

Metadata Update from @jnsamyak:
- Issue tagged with: high-gain, low-trouble, ops

6 months ago

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

6 months ago

Hey @carlgeorge!

Thanks for your request, I did create a release: https://bodhi.fedoraproject.org/releases/EPEL-10.0.

Please check if there is anything else, otherwise we can close this!

Note that with not-composed-by-bodhi and automatic updates, updates will go through and get tagged in, but since there's no compose, they won't go anywhere.

Is it planned to make a 'rawhide/branched' like compose of these or just have them land in the tag for some later date when bodhi composes them?

I would like to have a rawhide/branched-style compose of these.

I think we are all set with this issue, closing it now!
But if there is anything else, please feel free to reopen it :D

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 months ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog