Versioning for documentation to match daemon version
See original GitHub issueRight now the docs correspond to what’s on master
. We need docs for each daemon release so developers can see what’s available in the version they are using.
https://github.com/jimporter/mike may be helpful.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Versioning - Nuxeo Documentation
The Nuxeo Repository includes a versioning system. At any time, you can ask the repository to create and archive a version of a...
Read more >Compose file versions and upgrading - Docker Documentation
There are several versions of the Compose file format – 1, 2, 2.x, and 3.x. This table shows which Compose file versions support...
Read more >Version Control Guidelines - NCCIH
The author of the document will ensure the current version number is identified on the first page and, when possible, is incorporated into...
Read more >1.1 Getting Started - About Version Control - Git SCM
Version control is a system that records changes to a file or set of files over time so that you can recall specific...
Read more >Handling versions which change over time
In Maven repositories, changing versions are commonly referred to as snapshot versions. Snapshot versions contain the suffix -SNAPSHOT . The following example ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yes. i forgot about this when we were talking about lbry.tech docs. it shouldn’t block getting the docs up because we’re still pre 1.0, but it will become more important as the project matures. @eukreign @NetOperatorWibby keep this in mind when designing the docs system, but don’t worry about it too much yet.
Hi @moki1202 ! Any progress on this issue? The documentation is lagging behind by a bit and I would like to update it.