On Jan 20, 6:57 am, "Edward K. Ream" <[email protected]> wrote:
> Right now there are at least two critical issues with Leo's bzr trunk. For the first time in recent memory there were no new bug reports yesterday! It appears that the unicode problem may be fixed. I plan no new substantive work in this area unless further problems arise, except possibly for more checks as discussed below. We have had an enjoyable discussion of clones and error recovery. I plan to implement the rule that demotes data in external files containing @all directives. This may not completely fix the data problems arising from conflicting .leo and external files, but it should make such problems much more rare. The new rule is intended to make leoProjects.txt and leoToDo.txt less dangerous. There are still troubling aspects of the data problem. The problem appeared to trigger code related to old @file nodes. This is the only way, if I understand the situation correctly, that resurrected nodes could damage the data in the way that I thought I observed. In other words, I still have work to do. I plan to insert the following traces and checks. - Of unexpected execution of old file code. - Of clone resolution. - Of unexpected unicode situations. Some traces can be enabled permanently, others will perhaps only be enabled when --debug is in effect. On balance, I think releasing rc1 one week from today makes sense, though I am tempted to move the date closer. I'll try to resist the temptation :-) In particular, we had best make sure that the new clone resolution scheme won't cause unintended problems. Edward P.S. Please continue to hold commits to the trunk. Releasing a stable rc1 must have top priority at present. 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.
