ruby-shadow was retired in Fedora Rawhide [1]. Previously, in PkgDb, it would be obvious the package si retired. Unfortunately, from Pagure interface, I can't tell if the package is retired or not. I am not even sure if people can still commit to the branch or not. May be the "contributors" list should be displayed per branch if that is how Pagure actually works ...
[1] https://src.fedoraproject.org/rpms/ruby-shadow/c/f89ec82cec30ceb22aa497df5d737c49acd20955?branch=master
May be the "contributors" list should be displayed per branch if that is how Pagure actually works ...
That is not :)
On the right side, there is list of branches. If there was displayed just something like "list of supported/maintained" branches with possibility to display all nraches, that could do the job ...
So https://pagure.io/pagure-dist-git/pull-request/51 is making the branch name be gray if they are inactive. So retired packages will have their master branch inactive.
master
To make it even more obvious maybe we could add a label "Retired" near the title at the top.
Metadata Update from @pingou: - Issue assigned to pingou
This is great, would it be possible to hide (maybe with a toggle) all branches for EOL releases, e.g. el5, el4 and all Fedora releases before 26?
This appears to be implemented.
And this as well.
Thx for that.
I concur with @till, the branch list might be rather long and not useful.
Also, I'd love to be removed as a maintainer from retired packages ...
The package is not retired in EPEL7 and there is only one maintainer list for all branches, therefore it would not work for ruby-shadow currently. Not sure what happens with packages that are retired/eol on all branches. There it would be possible.
I think this is now clearer with the button to take orphaned package that displays "Retired" if the package is retired.
I'm thus inclined to close this ticket.
What do you think?
I think the UI changed, because the branch list is not visible by default anymore. But since there is the "Retired" button and there also is the list of recent builds, the situation is much better then it was, therefore I'm closing this ticket.
Metadata Update from @vondruch: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks
Log in to comment on this ticket.