; attention span over
)
)On 6/14/11 5:06 PM, Francisco Vila paconet@gmail.com wrote:
)
) 2011/6/14 Carl Sorensen c_soren...@byu.edu:
)
) I guess if we have documentation bugs it would be nice to have them
) fixed before release.
)
) Would a 1-week notification serve?
)
) Yes. If 2.14-x releases
On 6/15/11 6:21 AM, James Lowe james.l...@datacore.com wrote:
\
Does that also mean that you need me to do something (apart from hurry up and
get the patches for the doc bugs done!)?
When you push a patch for a doc bug that applies to 2.14, please make sure
there's a google code issue
Carl,
)-Original Message-
)From: Carl Sorensen [mailto:c_soren...@byu.edu]
)Sent: 15 June 2011 14:04
)To: James Lowe; Francisco Vila
)Cc: LilyPond-Devel list
)Subject: Re: 2.14.1 released; attention span over
)Importance: Low
)
)
)
)
)On 6/15/11 6:21 AM, James Lowe james.l...@datacore.com
On Wed, Jun 15, 2011 at 01:14:09PM +, James Lowe wrote:
I cannot see an option to add a 'backport' tag - for example I can see how to
add the 'Type-Defect' and 'Priority-medium' etc. But nothing with 'Backport'
in the string. So is there a specific way to do this?
at the moment, it's a
On 6/15/11 7:14 AM, James Lowe james.l...@datacore.com wrote:
Carl,
)-Original Message-
)From: Carl Sorensen [mailto:c_soren...@byu.edu]
)Sent: 15 June 2011 14:04
)To: James Lowe; Francisco Vila
)Cc: LilyPond-Devel list
)Subject: Re: 2.14.1 released; attention span over
, 2011 2:21 PM
Subject: Re: 2.14.1 released; attention span over
On Wed, Jun 15, 2011 at 01:14:09PM +, James Lowe wrote:
I cannot see an option to add a 'backport' tag - for example I can see
how to add the 'Type-Defect' and 'Priority-medium' etc. But nothing with
'Backport' in the string. So
2011/6/12 Francisco Vila paconet@gmail.com:
2011/6/12 Graham Percival gra...@percival-music.ca:
I've just uploaded lilypond 2.14.1. The stable/2.14 git branch
has diverged sufficiently from master that I'm not even going to
pretend to care about stable/2.14 any more. I'm bored with the
On Tue, Jun 14, 2011 at 09:07:01PM +0200, Francisco Vila wrote:
Graham; it would be _very_ appreciated if you'd announce a new stable
2.14-x release some days in advance. Thank you very much
As far as I'm concerned, all 2.14.x releases will happen when Carl
asks me to make one. I leave this
On 6/14/11 1:07 PM, Francisco Vila paconet@gmail.com wrote:
2011/6/12 Francisco Vila paconet@gmail.com:
2011/6/12 Graham Percival gra...@percival-music.ca:
I'll still make 2.14 releases -- just tell me to build a release,
and I'll do that based on the current stable/2.14 branch in
2011/6/14 Carl Sorensen c_soren...@byu.edu:
I guess if we have documentation bugs it would be nice to have them fixed
before release.
Would a 1-week notification serve?
Yes. If 2.14-x releases are to be frequent and/or numerous, this is
not so important. If we are going to live with a
On 6/14/11 5:06 PM, Francisco Vila paconet@gmail.com wrote:
2011/6/14 Carl Sorensen c_soren...@byu.edu:
I guess if we have documentation bugs it would be nice to have them fixed
before release.
Would a 1-week notification serve?
Yes. If 2.14-x releases are to be frequent and/or
I've just uploaded lilypond 2.14.1. The stable/2.14 git branch
has diverged sufficiently from master that I'm not even going to
pretend to care about stable/2.14 any more. I'm bored with the
number 14, and I have enough other things to pay attention to.
I'll still make 2.14 releases -- just
2011/6/12 Graham Percival gra...@percival-music.ca:
I've just uploaded lilypond 2.14.1. The stable/2.14 git branch
has diverged sufficiently from master that I'm not even going to
pretend to care about stable/2.14 any more. I'm bored with the
number 14, and I have enough other things to pay
13 matches
Mail list logo
