Streamline Rhasspy development on GitHub

I’m already loving the CI workflow we are building now. It has already found a bunch of small issues, like PyInstaller being incompatible with Python 3.8, version mismatches in dependencies, and so on. This will really allow us to iron out the kinks by finding all these issues (many of them corner cases) before users bump into them. We’ll have a really polished Rhasspy this way :slight_smile:

3 Likes

I added a “Proposed” column to the Roadmap project to separate interesting ideas that “could” get implemented from ideas that WILL be implemented.

Maybe a project for each major release can be more practical to clearly see when features/fixes are expected to be released…

What do you think?

Good idea of that Proposed column.

I think that milestones are better suited for a TODO list for a specific release, see the screenshot in that GitHub documentation page for how it would look. However, it seems that milestones can’t refer to issues and pull requests in multiple repositories, so these milestones should be made for each repository.

I do really appreciate all of the work you’re putting it! Yours is a very much needed skill on a project like this :slight_smile:

I like it. This fits nicely with how I tend to think of things anyways: as TODO or SOMEDAY.