2.0 release lineup and backlog

[thunderbiscuit]

This issue is a meta thread for refactors/ideas/features discussed in other PRs that might be out of scope in the short run for the 1.0 but should not get lost.

The past few dev calls have reminded us that in order to ship 1.0 stable we really need to focus and limit our scope when proposing changes that are meant for the beta/stable. It's easy to get new ideas/refactors on 5 new things whenever we open the codebase for one little change (looking at myself here with #1537). These things open up new discussion threads, require more review cycles, etc.

At the same time, a lot of these ideas/discussions are good and we wouldn't want them getting lost. Add posts here with stuff/links/discussions on things you want to keep in mind for the 2.0 or the 1.X releases. They might warrant full issues as well of course, but I was thinking of keeping track of them in a meta thread (if that doesn't work well we can just close it later on).

• Use explicit names for wallet builder methods that validate rather than set #1537 Cleaner workflow for loading private descriptors into wallet when loading from persistence.

[thunderbiscuit]

First one I want to mention is the renaming of the descriptors()/check_descriptors() method on the LoadParam, potentially including a boolean setting whether to extract private keys out of the given descriptors or not. See discussion in #1537.

I think it makes the API more explicit and forces users to understand better the persistence and load workflow, but also needs a bit of thinking/bikeshedding around corner cases (errors, conflicting booleans on different descriptors, etc.).

[thunderbiscuit]

Easier to use the tags and milestones.