This is currently the major obstacle I have to adopting RT1.
Ummm… how stable is RT2?
I use it daily. and it’s actually feeling pretty solid these days.
There’s a bit of robustifaction that needs to happen to the mail
gateway to make absolutely sure we don’t lose any mail.
I’ve looked at the buglist,
and I don’t see any real showstoppers. However, a lot of the
bugs are not not really clear to someone (like me) who isn’t
current on the development.
The closest things to showstoppers right now are the fact that
an administrator who isn’t careful can still break referential integrity
on some database objects. Big impediments to day-to-day use
include the fact that merge hasn’t been implemented yet, and that
RT still does all its time handling in GMT. Ivan’s been hacking on
an RT1 import tool, but it’s not quite there yet. (though this isn’t an
issue for you)
Is there an update to be made to
the “status.html” page?
Yep. I’ve been a bit busy with other things. Sorry about that.
Any idea on when RT2 will be feature complete?
That day gets closer and closer. I’m hoping to get alpha 4 out the door
next week. That should have a fully functional admin cli and fixes
for the nastiest of the bugs I know about right now (the ref. integrity
Will there be a non-“feature complete” release which
will have bugfixes?
The goal of each milestone release is to be more stable and complete
than the last. Generally, the point releases between each milestone
have improved stability too.
In short (and now I’m not asking Jesse to commit to anything,
but only for the opinions of people who test/use RT2), if I also
save all incoming and outgoing mail to a seperate maildir, what
are the risks I’m taking in using RT2 in a big production
environment that desperately needs a request tracker?
If you’re the daring sort, you probably want to save copies of all
incoming and outgoing mail and turn on SQL logging on your mysql
instance. If you do that, you should be pretty ok.
BTW, slight feature request (for RT3 ;-)): I think it would be
nice, when you’re consulting things in one queue, to have the
default selection of “New ticket” set to the queue you’re on.
Getting a bunch of the web ui’s selectors, etc to have ‘sticky’ preferences
within a session shouldn’t actually be too hard if you’re really interested,
I can give you pointers and will take a patch
Hope this answers some of your questions.
#include <std_disclaim.h> Lorens Kockum
rt-users mailing list
jesse reed vincent – email@example.com – firstname.lastname@example.org
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
T’waS br|ll1G 4|||> 7#e sl1T#Y T0v3s D1|> gYR3 4nd Gimb@1 1|| 7#E //A83
all |/|1|/|53Y W3R3 d4 60r0GR0V3s @|||> |>4 M0MES wr47H oUTGR4b3.