Learn more about these different git repos.
Other Git URLs
There's no reason this has to happen. Pagure has the API to work with issues. The admin scripts should just look for the oldest open ticket and start there.
When do you need this? (YYYY/MM/DD) Whenever possible
When is this no longer needed or useful? (YYYY/MM/DD) If we stop using SCM requests?
If we cannot complete your request, what is the impact? Minor annoyance to packagers
Hi, @qulogic thanks for reporting this issue. The fedscm_admin tool used by people to process the tickets does list the issues by the oldest and allow admin to process all the issues in the queue in that order.
Metadata Update from @humaton: - Issue tagged with: dev, low-gain, low-trouble
Yesterday, https://pagure.io/releng/fedora-scm-requests/issue/29949 was the oldest of my tickets open (possibly others were open too), but processing started at https://pagure.io/releng/fedora-scm-requests/issue/29969 which breaks since the repo request was before the branch request.
It might be that @limb processed a particular ticket manually by mistake?
Hi, so I opened PR fedscm-admin#52 last week that actually uses an API call that is sorted by the server. Sadly the test suite failed and I went on PTO. Going to fix it now.
This has been fixed upstream.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
But the above-linked PR is still open?
@qulogic, it was fixed just now. This was accidentally closed during releng meeting. here are bodhi updates with the latest package that should fetch sorted issues. f32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-468b9dcc17 f33: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d478c77847
Issue status updated to: Open (was: Closed)
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.