Adapt has been largely stable over the last 5 years, with the bulk of effort going into either mycroft-core, or padatious (a c++ ML-based intent parser). Given this stability, it makes sense to finally make a push for 1.0, opening the way to begin development on 2.0, without the baggage of maintaining backwards compatibility.
As part of the effort to get to 1.0, we'll have 3 major workstreams
There are currently 4 open PRs, languishing as far back as 2017. We should be able to complete or close these out quickly.
There are currently 30 open issues against Adapt. I'd like to triage these on the following dimensions
- Needs reproduction
- Can't reproduce, won't fix
- Reproducible, won't fix
- Reproducible, scheduled|in progress
- Fixed
- Deferred post-1.0
I'd also like to add the label of Adapt: Road to 1.0.0 to each of these issues, once they've been triaged.
Speficially, how/why we're transitioning to 1.0.0 to stable/supported, what the future looks like for 1.x, and decide where to branch for 2.0 development.
I'm adding a label for
Deferred post 1.0for a couple of things I've come across; MycroftAI/adapt#17 is old but fits the bill. I'm thinking the biggest chunk of work here right now is the docs revamp, and the more of them I've read the more work I realize there is to be done.