Malcolm Rowe wrote:
> On Sat, Jan 20, 2007 at 11:12:28AM +0000, Max Bowsher wrote:
>>>>> Could someone confirm what the effect of the current state on 1.4.3 is?
>>>>> I suspect that the answer is that the Perl bindings are still in the
>>>>> same state as they were in 1.4.2, and so we still need a merge of that
>>>>> final hunk in STATUS for 1.4.4. (Ironically, I think one result of
>>>>> this change might been that we managed to wrap the _Ruby_ bindings,
>>>>> something we didn't intend).
>>>> Actually I found a problem about this yesterday when i was trying a
>>>> fresh 1.4.x build, and was about to mail the list about the kind-of
>>> So what now? We have to re-roll the 1.4.3 tarball.
>> Could someone clarify what this means for 1.4.3?
>> Do we have an actual *regression*, or just some missing fixes?
> Missing fixes, I think. I'd be inclined to just pull the fix from trunk's
> CHANGES, update the 1.4.4 STATUS to include the missing parts of this fix,
> and release 1.4.3 as-is. Perhaps someone (CL?) could clarify exactly
> why this fix was important to backport in the first place (since it's
> essentailly adding new functionality to the bindings, I assume there's a
> reason it can't/shouldn't wait for 1.5.0).
Agreed. Unless there is an actual regression versus 1.4.2, I would like
to release the current tarballs as-is.
We can do a 1.4.4 in a week's time, if need be.
Received on Sat Jan 20 14:23:35 2007