Lute’s going well.
I’m not using Lute enough myself, so I’m losing a feel for what’s lacking as an end user, but that’s ok. At some point that will change.
In addition to the regular “keep the lights on work” – bug fixes and usability changes – there are a few larger items that should be dealt with.
Lute v3 has been going great! Users seem to like it, the install is so much easier than it was, and some people have made some great contributions, notably an audio player.
Lute v3 launched today. Wow, that was a lot of work, so nice to have it done.
Everything seems to be in order. Some final bugs and tweaks, several test runs. Release process updated. New pip and docker stuff pushed. Manual updated. User communication done.
I wonder if this thing will take off as much as I think it should. Guess it’s time to hurry up and wait.
In the meantime, I deserve a break.
Lute v3 is getting very very close to good to launch, if it’s not already.
Lute v3 is getting pretty close to ready:
- All tests ported: check
- All features implemented: check (I think)
- All obvious codo TODOs addressed: check
- Packaged and up on testpypi: check
- Dogfooded and user feedback implemented: not yet
- Documentation updates (porting, wiki updates): not yet
- etc …
So I guess it’s time to start dogfooding and to get some user notes.