Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Content] Pin docs to released versions

See original GitHub issue

Content request

For the time being we will be considering the substrate in the latest polkadot-x.x.x-release branch the most stable. Docs should thus use these as their baseline and work with these.

Are you willing to help with this request?

Maybe (please specify)

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

gnunicorncommented, Nov 3, 2021

Didn’t we actually decided to only have one doc page and that always points to master? To remove this entire versioning at all?

That is what you proposed and we are striving for eventually yes (although I don’t understand the urge to remove archived versions altogether, why?).

But we are talking about different time lines here: even once we have mastered continuous releasing for substrate telling people to always work against master with potentially daily breaking changes might not be feasible as the main entry point for people to start with. Meanwhile we can already take steps into the direction that will dramatically improve the situation until we’ve figured out the other problems along the way. This isn’t “either or”, it’s a “steps towards”.

0reactions

NukeManDancommented, Nov 11, 2021

I am leaning towards Polkadot release cadence (for now) - https://github.com/substrate-developer-hub/substrate-node-template/issues/260