Rt 2.1.8

RT Developers
1

RT 2.1.8 fixes some minor bugs in 2.1.7:
Removes extra files from the MANIFEST
Cleans up the config file installation (fixes problem with BSD install(1))
Removed an unneeded dependency or two from testdeps
adds a () to gettimeofday

It still doesn't note that it needs MySQL 4.0, rather than 3.23.

-j

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

2

|+ It still doesn’t note that it needs MySQL 4.0, rather than 3.23.

Since RT 2.1 (once fully available) will require MySQL 4.0, are there any
issues/concerns that should be pointed out while running an development
version of MySQL?

-darrin

3

|+ It still doesn’t note that it needs MySQL 4.0, rather than 3.23.

Since RT 2.1 (once fully available) will require MySQL 4.0, are there any
issues/concerns that should be pointed out while running an development
version of MySQL?

Keep good backups. I’ve not yet experienced any corruption, even during
power failures during write to the DB, but I can’t guarantee anything.
Once the schema stabilizes a bit, I’ll do a current postgres schema,
which should run cleanly on 7.2. I very much expect Mysql 4.0 to be GM
before the next stable branch of RT.

-darrin

rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

4

|+ Keep good backups. I’ve not yet experienced any corruption, even during
|+ power failures during write to the DB, but I can’t guarantee anything.
|+ Once the schema stabilizes a bit, I’ll do a current postgres schema,
|+ which should run cleanly on 7.2. I very much expect Mysql 4.0 to be GM
|+ before the next stable branch of RT.

I hope so. I have seem some quirky problems with 4.x with some of our
applications. Although we do keep good backups, on the 4.x server, we
backup even more.

During a recent billing cycle, our sql server experienced a crash. once
the machine was brought back up, we had lost ~2 weeks of billing
data. Luckily, we do keep backups, and we run 3.23 in parallel with 4.x
just to be safe.

Our billing database averages about 3600 rows per customer per month,
multipled by ~25 customers who has billing processed by this system.

-darrin

5

Thanks very much for the heads up. FWIW, what table handler were you using?

During a recent billing cycle, our sql server experienced a crash. once
the machine was brought back up, we had lost ~2 weeks of billing
data. Luckily, we do keep backups, and we run 3.23 in parallel with 4.x
just to be safe.

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.