[Feature Request] Enhance Release Information Display: Move Location & Distinguish Release Types
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- frontend
Research direction
Start with the project page represented by the linked projects-health-table dashboard and locate the existing release information at the bottom. Confirm where release data comes from, then move the section to the top and present major.minor.patch distinctions; done means the page clearly shows release visibility and type information, including maintenance-mode clues.
Written by the indexing model from the issue text.
Description
Issue Description
https://all.devstats.cncf.io/d/53/projects-health-table?orgId=1
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.
- Dominant language
- Shell
- Stars
- 130
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cncf/devstats
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
-
blocked enhancement
-
blocked enhancement
-
bug question
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100