I just said this in a comment for #334 <https://github.com/leo-editor/leo-editor/issues/334>, but I want to make sure everyone sees it. It applies to almost all the work that I do.
The code base [for Leo's importers] will be under considerable flux, but all should be well as long as all unit tests pass with the appropriate switches in their "legacy" positions. Doing the work in a separate branch *just delays the inevitable*. Indeed, once all my tests pass, I will be relying on problem reports from users to find *all* further problems. Pushing the new code base immediately ensures that *testing commences as soon as it possibly can*. Only those who are comfortable with git will be affected, so if real problems are found they can simply check out a version that works. Anyone disagree? 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
