Repository navigation
docs: drop the roadmap and the dated dependency snapshot - #46
Merged
Merged
Conversation
The roadmap table had six rows and every one said done, so it recorded history rather than plans. Its last row said CRAN accepted 0.1.2 on 2026-09-03, while DESCRIPTION has been at 0.1.3 since. The dependency section resolved its table against CRAN on 2026-07-31 and pinned four versions in the prose, then hand-counted a recursive set of fourteen packages. pak::pkg_deps() answers the same question and cannot go stale, so the section asks it instead. The reasons jsonlite, curl and tools are declared stay, because none of them is guessable. The compiled-code argument is in CONTRIBUTING.md in a fuller form, so the README keeps the conclusion and points there for the measurement. The citation section named 0.1.0 as the version to pin. CITATION.cff carries an identifier for every archived release, so it says that instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
biohttp is flat, so
README.mdis the GitHub front page, the pkgdown home pageand the text CRAN renders. 215 lines down to 177.
What was stale
done, 0.1.2 accepted 2026-09-03Resolved against CRAN on 2026-07-31, four pinned versionspak::pkg_deps("biohttp")The full recursive set is 14 non-base packagesVersion 0.1.0 is 10.5281/zenodo.21731865CITATION.cff, which has all threeThe roadmap had six rows and every one said done. A table where nothing is
outstanding is a changelog, and
NEWS.mdalready is one.Kept
The reasons
jsonlite,curlandtoolsare declared. None of them isguessable, and the
jsonliteone in particular explains a failure that onlyshows up at runtime on the package's main entry point.
The
Whysection stays. This is the page a CRAN reader lands on, and why thepackage exists is the thing they are deciding.
Moved
The compiled-code argument, including the 210ms against 0.2ms measurement, is
already in
CONTRIBUTING.mdin a longer form that names the alternatives. TheREADME keeps the conclusion and points there.
CITATION.cffneeded no change. It already carries one identifier per archivedrelease, matching what Zenodo holds.