Hi all,
2013/4/6 Janek Warchoł janek.lilyp...@gmail.com:
i think that its essential for us to first have a voice chat
about all the problems that we're currently having. I believe that
our problems cannot be effectively solved by mailing list discussions.
What do you think and when do you
With the recent batch of material with missing documentation, extensive
code changes and new functionality without previous exposure and moving
interfaces (like
commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7
Author: Mike Solomon m...@apollinemike.com
Date: Sat Apr 6 09:54:58 2013 +0200
On 6 avr. 2013, at 12:07, David Kastrup d...@gnu.org wrote:
With the recent batch of material with missing documentation, extensive
code changes and new functionality without previous exposure and moving
interfaces (like
commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7
Author: Mike Solomon
m...@mikesolomon.org m...@mikesolomon.org writes:
On 6 avr. 2013, at 12:07, David Kastrup d...@gnu.org wrote:
With the recent batch of material with missing documentation, extensive
code changes and new functionality without previous exposure and moving
interfaces (like
commit
Hi,
2013/4/6 David Kastrup d...@gnu.org:
master has stopped being suitable for turning into a
stable branch. There are several ways forward, none of them
particularly endearing.
[]
Developers simply can't be interested in doing and not doing what would
be important for a stable release.
Any option I forgot here?
Declare a feature freeze for a few weeks, with only trivial additions
and fixes for regressions and documentation issues.
And *no* development branch (except private ones). This should
enforce all parties to concentrate on the release, together with
proper testing.
Werner LEMBERG w...@gnu.org writes:
Any option I forgot here?
Declare a feature freeze for a few weeks, with only trivial additions
and fixes for regressions and documentation issues.
The time for a formal decision was too late, the more active developers
informally agreed to try and nobody
Declare a feature freeze for a few weeks, with only trivial
additions and fixes for regressions and documentation issues.
The time for a formal decision was too late, the more active
developers informally agreed to try and nobody bothered actually
doing so.
Hmm. We discussed that,
Werner LEMBERG w...@gnu.org writes:
Declare a feature freeze for a few weeks, with only trivial
additions and fixes for regressions and documentation issues.
The time for a formal decision was too late, the more active
developers informally agreed to try and nobody bothered actually
doing
- Original Message -
From: David Kastrup d...@gnu.org
To: Werner LEMBERG w...@gnu.org
Cc: lilypond-devel@gnu.org
Sent: Saturday, April 06, 2013 3:08 PM
Subject: Re: Stable release state
Werner LEMBERG w...@gnu.org writes:
Declare a feature freeze for a few weeks, with only trivial
Phil Holmes m...@philholmes.net writes:
At present, we're actually premature in proposing a freeze to make
ready for a release candidate. We have a number of outstanding
critical bugs and regressions which need fixing before we go anywhere
with a new stable release. So, currently, step one
David Kastrup wrote Saturday, April 06, 2013 10:07 AM
it is clear that master has stopped being suitable for turning into a
stable branch. There are several ways forward, none of them
particularly endearing.
a) cut the stable branch before the last batch of changes and accumulate
only
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: Werner LEMBERG w...@gnu.org; lilypond-devel@gnu.org
Sent: Saturday, April 06, 2013 3:26 PM
Subject: Re: Stable release state
Phil Holmes m...@philholmes.net writes:
At present, we're
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: Werner LEMBERG w...@gnu.org; lilypond-devel@gnu.org
Sent: Saturday, April 06, 2013 3:26 PM
Subject: Re: Stable release state
Phil Holmes m
During this two-month period, the only (non-documentation)
changes that may be made are changes that fix bugs or new ports
which do not require changes to other parts of the compiler. New
functionality may not be introduced during this period.
Yes! This is what I call a
15 matches
Mail list logo
