Comment #5 on issue 2338 by
d...@gnu....: OS X LilyPad not working
http://code.google.com/p/lilypond/issues/detail?id=2338
I am pointing out that OSX has now been responsible for about a month of
stable release delay. The people spending most of the time for fixing the
problem have no way of testing it. Any useful feedback even for total
blunders takes weeks to arrive, and arrives more by accident rather than
release-related coordinated testing, testing that does not require more
skills than actually using the respective platform. And that right before
a major release.
I think we owe the OSX users the following information in the release
announcement for 2.16:
a) since we don't have any actual users of MacOSX available for systematic
testing and feedback, support for MacOSX is only provisional. If any
component of it works, you are in luck.
b) without anybody willing to engage in regular, timely and systematic
testing, we have no option but considering MacOSX an unsupported platform.
While we will package MacOSX versions for the near future, there is no way
for us to know whether any part of them will actually work, and on what OSX
versions. For that reason, it does not make sense to have our release
schedule set back in case somebody actually happens to report a problem
short before a release. Without anybody willing to do systematic testing
and thus provide the most basic criterion for calling a system supported,
any problem occuring only in relation with OSX will not be considered
release-critical.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu....
https://lists.gnu.org/mailman/listinfo/bug-lilypond
opensubscriber is not affiliated with the authors of this message nor responsible for its content.