|
From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5699 LilyPond for GUILE 2.2 |
Date: | Tue, 28 Jan 2020 23:27:48 -0000 |
On Tue, Jan 28, 2020 at 11:57 PM David Kastrup
address@hidden wrote:
Our review process does not really work attaching multiple Rietveld issues to a single Sourceforge issue. If you want an encompassing issue for collecting several different/loosely related patches, the way is to use git-cl for creating individual patches/reviews, then create an additional overview issue with links to the various single Sourceforge issues. Otherwise, no one knows which patch is in which state of review/countdown/push as there is only one status per Sourceforge issue.
So we have a bug tracker, but we can't use it for tracking bugs ?!?!
--
[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 address@hidden 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 address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |