[CS-Project-devel] Updated layout for trunk, new releases, bugs found

[Dan F. <cra...@us...>]

*** TRUNK LAYOUT CHANGES ***
---------------------------------------------------

I've changed the layout of the "trunk" copy of cs-project.  There is now a
subdirectory for each version that is supported, similar to the "releases"
folder.  To retrieve the current development version of cs-project (v1.2.x
):::

OLD WAY::: svn checkout
https://cs-project.svn.sourceforge.net/svnroot/cs-project/trunk
NEW WAY:: svn checkout
https://cs-project.svn.sourceforge.net/svnroot/cs-project/trunk/1.2


*** NEW VERSIONS RELEASED ***
-----------------------------------------------------

The most current supported versions of cs-project are:::
VERSION 1.0:::  1.0.12
VERSION 1.1:::  1.1.1
VERSION 1.2:::  1.2.0-ALPHA2 (only in trunk)



*** BUGS FOUND IN PREVIOUS RELEASES ***
------------------------------------------------------------------------

While implementing a minor change to the login page and updating them to use
the newest version of CS-Content (v0.10.8) for each of the supported
versions, I ran through a couple of minor tests to ensure everything works.
Version 1.0.11 went just fine, with only a few minor template changes, no
major bugs found.  In version 1.0.0, I found a very major bug in the
helpdesk page: a fatal error appeared, indicating that it could not pull the
list of available tags.

Further investigation into the bug revealed that the "modifier" column in
the "tag_name_table" in the database wasn't present, causing a database
error.  The error caused an exception to be thrown.  Eventually I realized
that the installation schema lacked the extra column (along with associated
values).  The final change to the installation schema has not (as of this
email) been committed.

I would really appreciate if any or all of you could setup test
installations of each version (1.0.x, 1.1.x, and trunk 1.2.x) and perform
regular updates to test that they work.  It would really be nice if you
could also perform install tests (delete the config, drop the associated
database, and re-run setup).  Please reply to this email if you are willing
to do this for me.  I host my own web/database/dns server (
crazedsanity.com/buzzkill.org), so I can setup these websites (i.e. if
xofrevlis wants a test server for v1.0, I would setup "
v1-0.project.xofrevlis.crazedsanity.com"); as long as there's willingness to
occasionally test the server, I can build some test scripts to wipe-out the
config & drop the database.  But I *really* need to have human testing
performed.

-- 
Best Regards,


Dan Falconer
http://CrazedSanity.com || http://www.Buzzkill.org