It supports at most one active Rietveld issue per Sourceforge issue since the
progress of the changes in the Rietveld issue is tracked in the Sourceforge
issue. One can add material to the _same_ Rietveld issue but the result is
that the issue as a whole gets retested and reviewed, so if the early parts are
independently useful, this holds up their progress.
It's actually the same setup we had previously on Google Code+Rietveld.
---
** [issues:#5699] LilyPond for GUILE 2.2 **
**Status:** Started
**Created:** Mon Jan 27, 2020 08:21 AM UTC by Han-Wen Nienhuys
**Last Updated:** Tue Jan 28, 2020 10:57 PM UTC
**Owner:** Han-Wen Nienhuys
tracking bug for work to get LilyPond onto 2.2 without loss of functionality or
speed.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
