[Vxl-maintainers] Re: How close are we to getting a version 1.0 release out?

[<Pet...@es...>]

Below is an eMail of Ian Scott from September; how close are we now?


	Peter.

----- Begin Included Message -----

From: "Ian Scott" <ian...@st...>
To: <vx...@ro...>
Subject: How close are we to getting a version 1.0 release out?
Date: Mon, 24 Sep 2001 10:00:48 +0100

I believe that we are fairly close to being in a position to release version 1.0 of VXL

Summary:
This is a list of things I think need done.

- Add descriptions of the build process, downloading snapshots, and introduction to non-VXL modules (e.g. tbl, mul) to the VXL book - MAN will do this.
- Tidy-up and publish list of non-core documents - e.g. MUL and VGUI books.
- Make sure all tests do run correctly - MAN will do Windows platform
- Write some overview documentation for vipl and vepl
- Get CMake to deposit all libraries in one directory.
- Settle on one email reflector.

Optional things
- VIL rewrite (to use pointer arithmetic instead of index based addressing, and use view/data pattern)
- Improve fault-tolerance of vsl and io code - MAN will do this.
- move vcgl into vgl_algo.


Details:

Add descriptions of the build process, downloading snapshots, and
introduction to non-VXL modules (e.g. tbl, mul) to the VXL book.
An explanation of these important things somewhat exists in various places.
Manchester plan to add this to the book as part of VXL Coding session this
week.

Tidy-up and publish list of non-core documents - e.g. MUL and VGUI books.
We need to have a web-page that links to all non-core documents (and the
core ones as well.)

Make sure all tests do run correctly.
The tests all compile at present - but they do not run without errors.
Manchester will have a go a fixing these for Windows and Linux/GCC platforms
during a VXL coding session this week.

Write some overview documentation for vipl and vepl
Image processing is kind of important for a computer vision library - we
should tell people about it.

Get CMake to deposit all libraries in one directory.
Talk about doing this has appears in the past on the reflector.

Settle on 1 email reflector.
Currently we are using the vxl@robots.ox reflector. We have set up a set of
email lists on the SF reflector. If we are going to move to the new
reflector, we should do so soon - and certainly before releasing VXL 1.0.
The various bug,feature,support trackers on SF should also be linked up to
the email lists. The old reflector could be reprogrammed to reply describing
the new reflector to senders.

Optional things
VIL rewrite
To use pointer arithmetic instead of index based addressing, and use
view/data pattern. Talk about doing this has appears in the past on the
reflector.

Improve fault-tolerance of vsl and io code.
vsl aborts if the input file is corrupted - not sensible. Manchester plan to
fix this  as part of VXL Coding session this week.

move vcgl into vgl_algo.
There is only one thing in vcgl - it doesn't need a library of its own when
it would fit well into vgl_algo.

Ian and Tim.


----- End Included Message -----