The migration of the tracker from GC to Allura at SF has gone well. Attachments are present and searches work (in the Allura style, which takes some getting used to, but is pretty comprehensive.) I've set up some common searches to make things easier. You can view it here to inspect and play with no need to register or log on:
https://sourceforge.net/p/testlilyissues/issues/ At present just Phil and I are installed as Admins. We now need to bring the DB up to date with the changes notified on the bug list since 24 Aug before they all get forgotten. I suggest one of the bug squad members does this. Simon would be best, as I think he created most of the recent ISSUEs. Whoever does this needs to register with SF and join the LilyIssues (testlilyissues) project as a member. To do this, go the the url above, click on join, and fill in the details. Make sure you untick the "Receive newsletter" box. I would recommend using a throw-away email address so you can make a clean break later if you are spam-averse. Then email me the username you have chosen so I can give you Dev status. The new Issues will need to be entered (pretty obvious, really) in the correct order, as the number cannot be specified. Then any subsequent comments from the bug list will need to be added by proxy, adding the name of the real author in a text comment. @James: you may like to register in the same way so you can gain some familiarity with Allura and bring the Patchy and push details up to date. You may even be able to use it to help with the countdown this weekend. Trevor _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
