Sorry for your inboxes. Now that I’ve accepted we’ll have over 2k issues forever, open issues for all of the things:
I’ve been watching as the libs team has done something great for the last two cycles: choose a set of things to work on, and then come back to it at the end, making sure it all got done, or punting on things for later.
There isn’t a ‘docs team’ yet, but I’m going to try to do the same thing, starting with 1.6. The 1.6 docs issue will be filed after we branch off 1.5, but here’s a master checklist to make sure that we cover everything at least once before focusing on improving something that exists.
A lot of this already has a lot of good docs, I just want to make sure that we do the entire thing at least once. Lists are good for that.