On Thu, 2010-01-28 at 11:08 +0100, Steffen Mueller wrote:
Hi Steffan, List Lurkers,
> > Right.. it's a bit like that.. I had a patch waiting for ages for
> > someone to check out in the end I added it to trunk. It was very simple
> > really, nothing like what you're doing, but it's the same end result..
> > it's not noticed until it hits trunk and then a release.
>
> It's not really surprising either. We're a volunteer group. I think all
> of us are in it for our own enjoyment. Testing branches is no fun.
True, I still haven't made the switch.. you know, it's all too hard.. :)
> Given that we're usually using the frequent Padre releases to whittle
> out bugs ("the problem manifested between 0.38 and 0.39." vs. the more
> usual "bisection tells me the problem manifested with change 10000") and
> that's probably a difficult to break habit (cf. comment about volunteer
> groups) it's probably better to push out a 0.56 release without my
> dubious changes.
>
So the big question is, how available are you going to be during the
cycle between the release of 0.56 and the merge of your branch to 0.57?
It looks like the issue Sebastian was seeing might not be a blocker for
a 0.56 release...
So in terms of 'managing' releases here, lets get the last of the
changes in for 0.56 in. We can release with all the improvements we
have already and look to making the merge of your branch as the primary
focus of development for the 0.57 release.
This shouldn't hold people up too much... ?
Pete.
PS, I'm changing ISP's soon, I might be off line for a bit as I sort out
mailing list membership.
_______________________________________________
Padre-dev mailing list
[email protected]
http://mail.perlide.org/mailman/listinfo/padre-dev
