You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, release information is displayed at the bottom of the project page. It would be helpful to move this information to the top of the page and distinguish between different types of releases (major, minor, and patch) following the format major.minor.patch. This change can clarify the project's status, especially in maintenance mode (i.e., minor releases have stayed the same in the past few years).
Proposed Solution
Move the release information section from the bottom of the project page to the top, making it more visible to users.
Distinguish between different release types (major, minor, and patch) to give users a clearer understanding of the project's status.
Benefits
Enhanced visibility of release information.
Allows users to identify when a project is in "maintenance mode."
Improves the overall user experience when browsing the project page.
The text was updated successfully, but these errors were encountered:
Hey, @onlydole I will try it. Thank you, for writing it beginner friendly but I didn't understand how to distinguish between different types of releases (major, minor, and patch).
I saw the releases at the bottom but there were no major, minor, and patches mentioned. How to know about them.?
I have no other info that just last tag matching regexp for given project's main repo.
If you provide an algorithm how to get (2) from this, then I'm happy to help.
I can do 1 anytime and 2 once specs are clear.
Any new features, especially for project healths dashboard need @caniszczyk 's approval/green light.
Issue Description
Currently, release information is displayed at the bottom of the project page. It would be helpful to move this information to the top of the page and distinguish between different types of releases (major, minor, and patch) following the format major.minor.patch. This change can clarify the project's status, especially in maintenance mode (i.e., minor releases have stayed the same in the past few years).
Proposed Solution
Benefits
The text was updated successfully, but these errors were encountered: