Add links to GitHub downloads
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github, html
- Domain
- documentation, release
Research direction
Start with the Boost 1.81.0 release notes page and inspect the Downloads section and the website source that generates or contains it. Add GitHub release links for Boost 1.81.0 onward below each downloads table, then verify the displayed links point to the corresponding GitHub release pages.
Written by the indexing model from the issue text.
Description
It would be nice to add GitHub download links in release notes starting with Boost 1.81.0.
For example, on 1.81.0 release notes page, add a text like "Source packages with git layout are available on GitHub." below the downloads table in the Downloads section.
The archives on GitHub are useful for people using Boost in CMake. They lack the unified boost include directory and require the user to either recreate it by running b2 headers or specify library include directories in the compiler command line (which is what CMake does).
- Dominant language
- HTML
- Stars
- 29
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 boostorg/website
-
search UI frozen Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in boostorg/website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#167 ·
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·