#8754 Fedora 32 Bodhi updates are set to be 3 days in testing
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by churchyard.

Describe what you would like us to do:

According to our policy, all non critical path updates MUST either reach the prescribed karma level for that update, OR spend at least 7 days in updates-testing before being allowed to go to stable.

However, it seem that F32 updates are set to be in testing for 3 days only.

Examples:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-c944120d0c
https://bodhi.fedoraproject.org/updates/FEDORA-2020-9f49879a9f
https://bodhi.fedoraproject.org/updates/FEDORA-2020-83600ebca3

Please set the updates to be 7 days in testing.

When do you need this to be done by? (YYYY/MM/DD)

ASAP before the final freeze.

I've cross posted this to https://pagure.io/releng/issue/9331 -- please close the wrong one.


I updated things, but those updates are still showing 3days for some reason.

@cverna any ideas?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

4 years ago

Yeah so the value displayed on the web interface is persisted in the database. This value is set at the update creation, by default it takes the number of days associated to the release (coming from the bodhi config file) or packagers have the possibility to extend that if needed or wanted.

I could update the database to set them to 7, but they are already requested for stable so are we happy to let these 3 go or should we try to fix it ?

If I understand that correctly, you are talking about the already existing updates only? I'd keep them.

I'd just say good enough... existing updates with the old threshold would be going stable in a few more days anyhow...

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

4 years ago

Login to comment on this ticket.

Metadata