Planning for 1.2.0 release.

[Bernhard Reiter]

So what do you we need to do to get 1.2.0 out of the door?

Browsing our problem tracker at wald, here are the issues that I think
we should address before releasing 1.2.0:

97 problem accessing database tables with 1.1.0 version : wx 2.6 problem
98 problem accessing database tables with 1.1.0 version : point layers
118 problem with utf8 systems trying to see non utf8 table

We must look into the postgis failures I had on Debian Etch (see my post
a few minutes ago).

In addition I think we should fix the packaging for Debian Etch as well.
Anything that I have missed?

Barry, I have not heard much from your in the last days,
so I am assuming that your changes should go in for 1.2.1
or a development release 1.3.0, so people can test your stuff.

There is no timeframe for the 1.2.0 release, but because the last
release was so long ago, I want only critical problems to delay
it and it will be published when it is ready.

Bernhard

-- 
Managing Director - Owner, www.intevation.net       (Free Software Company)
Germany Coordinator, fsfeurope.org       (Non-Profit Org for Free Software)
www.kolab-konsortium.com   (Email/Groupware Solution, Professional Service)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20061106/f47fe414/attachment.bin