On Sun, Oct 29, 2017 at 3:16 PM, Terry Brown <[email protected]> wrote:
> How best to track issues for > l > arge sub-projects like leo_edit_pane? > > I'd like to drop of lot of LEP related issues into the Leo issue > tracker, but could understand if there was resistance to that, so: > We are thinking exactly alike. Imo, the solution is to create a LEP issue page that links to as many subsidiary pages as you like. I have created the Sub-Project label for that purpose. Feel free to create a LEP label. Less preferred options: > > Track them on LEP's project page. I'm not too excited by GitHub's > projects I agree. They are feeble. Another option: > > Use a separate, empty, repo. to isolate them and keep them out of the > main issue list - ok if having them in the main repo.'s undesirable. > I hadn't thought of that, but I think using Leo's issue tracker will be much better for collaboration. Another option: > > Something using milestones, although I only "all issues for milestone > X" view, no sign of an "all issues *except* for milestone X" view. > Again, I hadn't thought of that, but issues should work better. In short, issues and linked sub-issues should work just fine. I shall use this approach for Jupyter-related notes and discussions. 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.
