diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fcd0f1971..a8e463707 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -78,11 +78,11 @@ issues and writing documentation are just as important as writing code. We can't fix bugs we don't know about, so good issues are super helpful! Here are some tips for writing good issues: -- If you find a bug, make sure it's still a problem on the `main` branch. +- If you find a bug, make sure it's still a problem on the [`main` branch](https://github.com/uutils/coreutils/releases/tag/latest-commit). - Search through the existing issues to see whether it has already been reported. - Make sure to include all relevant information, such as: - - Which version of uutils did you check? + - Which version or commit hash of uutils did you check? - Which version of GNU coreutils are you comparing with? - What platform are you on? - Provide a way to reliably reproduce the issue. diff --git a/README.md b/README.md index e770bd543..f05bf77ea 100644 --- a/README.md +++ b/README.md @@ -29,8 +29,9 @@ options might be missing or different behavior might be experienced.
-We provide prebuilt binaries at https://github.com/uutils/coreutils/releases/latest . -It is recommended to install from main branch if you install from source. +We provide prebuilt binaries, manpages, and shell completions from main branch at https://github.com/uutils/coreutils/releases/tag/latest-commit . +The latest stable tag https://github.com/uutils/coreutils/releases/latest exists only for reproducible products and packagers. +You should use binary from latest commit generally.