dropbox / dropbox/rust-brotli

Delete GitHub releases or make them for new tags

Open
#261 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
943
Forks
109
Avg merge
8d 3h
Merged PRs (30d)
1

Description

Very soft suggestion, it seems that for a long time only tags are created without releases. It means when first landing on this repo, it looks strange.

Image

Latest release 7 years ago, which made me think the project isn't maintained since it's the first text I look at for any repo before the README. After some more searching including for alternative crates, eventually I realized the latest version is 8.x, not 1.x, and the project is well maintained.

I can understand not publishing a release with each tag - in that case, how about deleting the old releases completely? They are just GitHub metadata, tags will remain, and presumably 7 year old metadata isn't being used so could be safe to delete. Then there won't be any "latest release" called out in that UI and we can examine tags / README when landing on the repo.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source files or tests are named. Review the repository's GitHub Releases and tag history first, then decide whether the project should delete old releases or create releases for new tags; done means one clear release-management policy is chosen and applied.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.