I’ve rolled the rt 2.1.2 release. I’m not actually convinced that it came out
right. I’m running into some issues with aegis involving it being unable to
properly reproduce historical revisions. Some of these issues are fixed in
yesterday’s release of aegis, but not all of them. While it seems to do the
distributed thing very well, it doesn’t have all the magic-bullet qualities I
want out of a version control system. (Among others: it supports a "move"
operation, but it turns out that the move operation is just a rm and a create,
so you don’t get full history preserved.)
But anyway, back to RT.
THIS IS AN INCREDIBLY UNSTABLE DEVELOPMENT RELEASE.
IF YOU ATTEMPT TO USE THIS RELEASE IN PRODUCTION
YOU WILL GET NO SUPPORT OR SYMPATHY. NONE. I WILL
POINT AND LAUGH.
2.1.2 contains some major changes at the source level:
* Moving to a new overlay-based model for the code, which will allow better automatic generation of automatic code. This currently means that RT 2.1.x is dependent on Perl 5.6.0 or newer. I haven't yet put in the energy to determine the cost of continuing to support 5.005 and earlier revisions of perl. Keeping in mind that 2.2.x probably won't ship until close to 2003, when 5.8.x are the "standard" revisions of perl, I'm not sure how much this legacy perl compatibility would be worth. * Keywords subsystem has been removed. The schema and base classes for the new "Custom Fields" system which will replace it in its entirety are there, but not yet functional. * A Test suite! "make test" will perform a basic smoke-test which makes sure that all of RT's perl code compiles. "make regression" will run the (Currently paltry) regression test suite which will DESTROY your rt22 database and run tests against a clean db. Eventually, this test suite will fully exercise the RT core. * Postgres and oracle schema aren't current. There's a lot of flux in the 2.2 schema right now. As things settle down, I'll bring the schema for pg up to date. Oracle support will either be updated or expunged. * Lots more perldoc (thanks to the new overlay system) * Unattended installation the install and build process now does much more of its work in pure perl, which means that we're getting closer to the day when actual automated installation is magic.
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.