What to release? (wasy: DBFSet_atof_function resolved (again =))

[Didrik Pinte]

On Thu, 2008-01-03 at 10:39 +0100, Bernhard Reiter wrote:
> So I am still wondering which version to release for Thuban 1.2.1
> (which I would want to release quite soon).
> Candidates:
> a) Not merge the new pyshapelib back to trunk
> b) use /thuban/branches/WIP-pyshapelib-Unicode/thuban at 2795
>    Drawback: potentially LC_NUMERIC unstable, which is a regressing
>    less tested then
>    Advantage: More test exposure with the new code.
> c) use /thuban/branches/WIP-pyshapelib-Unicode/thuban at 2798 2799 or later
>    Drawback: in development, so not tested and ready for a real release.
> 
> Before christmas b) seemed to be the best guess, I am now wondering if a)
> is better so we can properly wait until the waves for c) are done.
> Nothing keeps us from doing another Thuban release once we see fit.
> 
> What do you think?

I think a) is the best. The LC_NUMERIC problem is really annoying and
cause strange things for the end user. Thus, I go for a) and c) as soon
as it is stable enough (that can be very soon ;-)).

Didrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20080103/253782e4/attachment.bin