- New changes use new plugins, all of which are almost perfect, none of which are good enough. I can fix each of them myself, and release, however doing that work, which IS wasted, is not a priority.
- In sussing out those plugin issues, I burned quite a bit of time on them.
- I moved a few more issues into the release and performed the bulk of that work, which took a while.
- The two new libs that the new code uses aren't 100% and aren't released yet, either.
- I need to do some further design work on the final aspect of the changes, which is core to the release.
- I spent the last 5 days making myself independent of currently available loading solutions, none of which were up to my (admittedly very high) standards.
- Although I did most of the translation base stuff, I didn't complete it due to "future" changes in various parts. I still need to do that work.
- I currently have 4 branches based off of the end of my private changes, most of which are data tweaks for custom logging. I want to break free of that shackle and get down to just one as rebasing four mixed branches when something on the public base changes is a slight pain.
If any of the plugins get released/fixed in the mean time, I'll push the associated changes ASAP and retain the remaining stuff locally.
IE, I'm releasing what I can cleanly release. To push changes prematurely would mean pointless repository churn tweaking things that I already knew were wrong...
Fred.