[GUSDEV] 6/3 GUS 3.5 Development Status

[Michael S. <msa...@pc...>]

IMPORTANT PRE-3.5 STATUS REPORT NOTE:

GUS 3.5 is nearing completion.  Before releasing it, the 3.5 branch in CVS
will need to be merged back into the main trunk.  This will be easiest if
CVS access is restricted.  THUS:  Please be prepared to commit all changes
to CVS by the end of next week (regardless of which branch you're working
in).  It's very highly likely that CVS will be restricted early the
following week for the merge and anticipated release of GUS 3.5.  More
details to follow as we get closer.

GUS 3.5 Development Status

This is an updated 3.5 status report. As always, please let me know if you
have any questions or concerns.

Important!=A0 While components of GUS 3.5 are finalized and the overall syste=
m
is nearing release, it is NOT YET READY=A0for use and attempting to do so in =
a
production environment, or even in a test environment in which GUS 3.0
exists MAY RESULT IN DATA LOSS.=A0 You have been warned!=A0 Do NOT=A0use the GUS
3.5 cvs branches for any other purpose than GUS 3.5 development, and only
after having read and fully understanding the relevant documentation.

* Schema

Completed and frozen for release.

See the Administrative Functions for a few small notes that tangentially
affected the schema.

* Plugins

The plugins still represent the largest body of work remaining for 3.5.
We're moving closer, especially thanks to the hard work from Jennifer Domme=
r
and Debbie Pinney.  Most of the Plugin development team feels that remainin=
g
plugins will be completed by 6/10.

* Application Framework

There were a few small changes this week in the application framework,
mostly to address Java compile issues.  I believe the application framework
to now be stable and complete, pending any yet-to-be-discovered bugs.

* Administrative Functions & Installing

The configuration for the administrative framework has been updated so that
tables use NUMBER datatypes for housekeeping columns instead of CHARACTERS.

An oversight was addressed that prevented the CHARACTER datatype from havin=
g
any length greater than 1.

Many tables were renamed in the gus_schema.xml file to fix capitalization
issues.

The bootstrap data issue has been resolved by required plugins to bring wit=
h
themselves any trivial CVs.  See related emails from this past week.

I believe the administrative functions and installer to now be stable and
complete, pending any yet-to-be-discovered bugs.

* Documentation

The install guide is nearing completion-- I expect it to be done Monday.
The developers and users guides will be next, and hopefully completed by th=
e
end of next week.

* Upgrading

No changes.