PSA: Don't use moving targets as release names
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
I noticed there are a few packages that use branch names, or something like `latest` as their release version. Please don't do this; mason doesn't automatically update those releases when the source code changes, so a `latest` package is outdated very quickly.
If you want to create a package that is not an actual release, please use a date and/or a commit hash as the version name, e.g. [`rapidjson 2016-07-20-369de87`](https://github.com/mapbox/mason/tree/master/scripts/rapidjson/2016-07-20-369de87). While the commit hash is enough for uniquely identifying the release, adding a date means that it's easier for humans to figure out what the newest release is.
/cc @springmeyer @jfirebaugh @mikemorris @brunoabinader @rclark @flippmoke @artemp @mourner @morganherlocker @tmpsantos @mapsam @yhahn @lbud @danpat @ansis @bleege @bhousel @TheMarex @1ec5 @daniel-j-h @friedbunny @ajashton @BergWerkGIS @camillacaros @mapbox/cpp
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.
Research direction
The issue names no files, tests, or entry points. Inspect mason's package release and version-naming workflow for branch names or moving labels such as `latest`; done means non-release packages use a date and/or commit hash and no longer rely on moving targets.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100