RT 3.0.10 Release Candiate 1

I’m pleased to announce the first release candidate for RT .3.0.10. A
full changelog is included below and a final release is expected within
the next one to two weeks.

Jesse

Web interface
Significant performance improvements for ticket history display
Applied patch to correct logic in SelectMatch
MessageBox is now more configurable
Update to force language handle change when the user sets it
Fix for overly agressive email ‘signature’ truncation when
quoting
messages
Fix for repeated signature addition when creating tickets with
attachments
Don’t hide ticket updates for negative amounts of time
Fix for the “quicksearch” which was occasionally broken in 3.0.9
Small change to fix escaping for saved searches
Improved Apache2 compatibility

Core
A fix from Ruslan for getting values for a named global
Custom Field
Split Sendmail arguments properly for mail sending
Improved descriptions of merged ticket in history
Additional debugging when ticket creation fails
catastrophically.
Make custom field names case insensitive in TicketSQL
Better cleanup of temporary files
Better emailing of error messages after "permission denied"
errors

Internationalization
Updated Finnish localization
Minor corrections to French localization
New Danish localization
New Hungarian localization

Database
Updates to oracle CLOB handling

CLI
Fixed a couple small ticket update bugs with the cli

Developers
Added callback for adding new users
Exclude svn cache files from regression test suite
Deslashified bits of the styleguide
Better logging of failed thawing of search queries

Hey Jesse,

Is it expected that the truncation function for the db-inserts/updates of
varchar’s [1] will be part of 3.0.10? Or is this a low priority thing? I
would say it’s fairly important, since it might cause mails to get bounced,
as well as other database updates to fail randomly.

– Robbert

[1] http://lists.fsck.com/pipermail/rt-devel/2004-March/005466.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Jesse,

Is it expected that the truncation function for the db-inserts/updates
of
varchar’s [1] will be part of 3.0.10? Or is this a low priority thing?
I
would say it’s fairly important, since it might cause mails to get
bounced,
as well as other database updates to fail randomly.

It’s not currently on the list for 3.0.10, but I really do believe that
it’s actually a change to DBIx::SearchBuilder::Handle::Pg to perform
database introspection. Patches are, of course, appreciated.

Best,
Jesse

– Robbert

[1] http://lists.fsck.com/pipermail/rt-devel/2004-March/005466.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFAWJWeQaM/s3DrrJARAopGAJ9QbYbSHHx1XaBN+zSIgJeQPCGTCgCbBAJG
UiQErZQNV570uO0/h44eBR4=
=vU/D
-----END PGP SIGNATURE-----