After a week working on 5.7 final, I am not at all satisfied with the profit/effort ratio. Here are preliminary thoughts. Your comments are welcome.
Now that `pip install leo` is feasible, I believe we can emulate Jupyter's install page <http://jupyter.readthedocs.io/en/latest/install.html>. This approach would have the following benefits: - Instructions are simple, shorter and clear. - No need for sourceforge, pyinstaller, windows installer. Otoh, we might still want a discussion of using git ;-) >From my point of view, about the only advantage of using official releases is that it forces me to update documentation. But that is fading in importance now that we use the github issue tracker for almost all improvements and bug fixes. Rather than laboriously editing the release notes we could do the following: - Insure that all bug fixes and enhancements are recorded in the issue tracker. - Mark all completed items with the proper release milestone. - Mark all significant items with the lvl:major label. In fact, I did this for 5.7, excluding the lvl:major label. Edward P.S. I am not happy that the two latest comments about Leo on sourceforge are from those unwilling or unable to install Leo. I would rather delete the entire evaluation section, but that seems impossible. This is one reason I am thinking of abandoning sourceforge. The other is that very few people use it. My time is limited, and I would rather work on Leo than on seldom-used distros. EKR -- 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.
