The two space shuttle disasters are a clear warning that schedule goals can be the enemy of quality. I vividly remember the embarrassment of releasing a beta version of Leo that had an horrendous data bug.
Right now there are at least two critical issues with Leo's bzr trunk. The first is the unicode problem with encodings other than utf-8 that zpcspm has just reported. The second is something that happened to me last night, traces of which are visible in recent commits. The trunk got out-of-sync on two of my machines, and it took over an hour to reconcile them fully. I had to clear the cache and sync both copies of LeoPyRef.leo. Cross-file clones, caching and resurrected nodes all contributed to the problem. Furthermore, LeoPyRef.py can get out-of-sync with leoPy.leo. There are just too many copies of what is supposedly the same data floating around. Two recent changes may have contributed to the data woes: 1. I recently changed my work flow. While working on a task, I would leave a clone of the present task in the to-do file (leoToDo.txt), so the changing code appeared in at least two places. This could have put great stress on the code that tries to decide which version of differing clones to use. 2. There were crashes while I debugged the new version of write_Leo_file. They might have corrupted test.leo, but I also reverted parts of the trunk. These reverts might confuse the cache. Here are some palliative measures I plan to take: 1. I am considering removing leoProjects.txt from the repository. Indeed, it is irritating to have the diffs muddied by the clones in this file. 2. I'm going to make it a personal rule never to put clones in the to- do file. At present, neither the projects file nor the to-do file contain any clones. 3. I shall consider banning cross-file clones, that is, clones that appear in multiple *external* files. This would make @view nodes more urgent. This probably will happen after Leo 4.7 final. Sorry about this. I hope to resolve both issues this week, and release the next version (whatever it is called) next week. Imo, at least one week of testing on a stable trunk is required before the next official release. Edward
-- 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.
