For the last few days I have been transitioning devel to Leo 6.5. The devel branch is now stable and usable.
I shall announce Leo 6.4 widely this Friday, September 24. This slight delay will give Félix and me a bit more time to get everything ready. The transition to the new unit testing framework is going well. In particular, I now use test-all.cmd to run all unit tests *outside* of Leo. Very convenient for testing PR's. Here it is: cd C:\leo.repo\leo-editor python -m unittest *Goals for this year* 1. To be mentally ready to support leoInteg. 2. To release Leo 6.5 final asap, somewhere between October 15 and December 1. All remaining issues are minor and will take hours, not weeks. In particular, ongoing Qt6 follies do not affect leoInteg. *Life after Leo 6.5* The future is murky, but surely it will involve programming. Leo is about to be *finished*, not just complete. I have no firm commitments to Leo's python code beyond Leo 6.5. I have started telling people that if they want a new feature they had best create a PR. I'll avoid make-work so that I can be mentally ready to explore new directions. One likely area for exploration is working on vs-code/leoInteg plugins. We shall see. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9a99f3ab-bd58-4d0e-8e38-54e99ba35438n%40googlegroups.com.
