I plan to release b2 today or tomorrow. There is only one more bug on the b2 list: it involves @root nodes.
I've moved a few items from the b2 list to the b3 list. I would like to release b3 next Friday, and continue to release betas each Friday until there no serious bugs on the bug list. Imo, it's important now to release every week so that distribution-related issues can be resolved. Such issues tend to hide until releases :-) A new thought came to me this morning: the time it takes to finish a release is related to the riskiness of the items on its to-do list. The riskier items should be done early so they can be tested. For b3, there are at most one or two items for which fixes are non-obvious. I'll do them immediately after releasing b2. So, despite the usual delays, I do believe we are making progress towards Leo 4.6 final in 3-4 weeks. Edward P.S. The items on the b3 list, in approximate order of priority: - Fixing rst import annoyances. - Fully resolve unicode issues. - Getting the new colorizer working solidly. - Various items in the bug tracker. EKR --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
