Peter Lavender wrote:
>> 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?
Hard to tell. Currently, I'm doing all volunteer programming work on a
pretty erratic schedule. I can't commit to anything, unfortunately.
> 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.
I think I prefer it this way, too.
Cheers,
Steffen
_______________________________________________
Padre-dev mailing list
[email protected]
http://mail.perlide.org/mailman/listinfo/padre-dev
