How close is Wakaba to a finished project? That is, from "not updating in the forseeable future" to "a update will be out next week", where does it stand?

I ask because I want to make some changes, but:

1. I don't want to try and integrate them.
2. They're almost certainly less valuable than changes you guys would make.
3. They're rather contrary to how it works, so integrating them into the main code would be a bad idea.

I mean 1. integrate them into new updates.

>>1

1. Go look at relase dates. There were about six in almost two years.
2. Get yourself familiar with version control systems like CVS, Subversion or whatever. Making local changes while keeping track of upstream releases is a hell lot easier with them -- most changes are non-conflicting and will be merged automagically. There was even brief intro about this matter in CVS documenation.

There hasn't been a release in quite a while, so it is pretty finished. There are a few bugfixes that are still outstanding, and likely there are undiscovered bugs to still fix, and I hope to get that stuff done SOMETIME, but mostly it's quite stable.