|
From: | Martin Tarenskeen |
Subject: | Re: merging philomelos musicxml2ly-dev |
Date: | Sun, 13 Jul 2014 15:57:15 +0200 (CEST) |
User-agent: | Alpine 2.11 (LFD 23 2013-08-11) |
On Sun, 13 Jul 2014, James wrote:
I have no preferences either way - we have done this for articulate.ly for instance - but unless we know that philomelos and LilyPond's versions are reasonably close to start with we could end up with each version becoming so far apart in terms of codebase that nothing gets fixed or that LilyPond's musicxml2ly becomes so far behind philomelos to be worse than useless and we might as well remove musicxml2ly from the code and just point to Philomelos.
Would it be an idea to freeze development of musicxml2ly until the Philomenos improvments have been merged with Lilypond's "official" version?
This is already the defacto situation? There haven't been much changes for months on both sides I think?
-- MT
[Prev in Thread] | Current Thread | [Next in Thread] |