RT3.0 timeframe

I’m not sure how to ask this delicately, but when do you estimate that a
near final release of 3.0 will be done? I’m several days into setting up
RT2.0 for our needs, but if 3.0 is going to be stable soon, I want to
follow that branch now instead of doing an upgrade in a month.
I understand there probably isn’t a market driven release date like other
software, but I’m looking for some idea so I can make an informed
decision.

Also, is anyone successfully running either version with Apache 2.0? The
README for the beta says that it is supported, and we would prefer to keep
as close to the default installation of RH8.0 as we can. Currently I’m
using a version of 1.3.x.

thanks
-james

Also, is anyone successfully running either version with Apache 2.0? The
README for the beta says that it is supported, and we would prefer to keep
as close to the default installation of RH8.0 as we can. Currently I’m
using a version of 1.3.x.

I had RT3 running under Apache2 a few weeks ago, it seemed to work fine.
For reasons unrelated to RT3 I ended up deciding that Apache2 was still
too new for production (sigh) so I switched back to 1.3.x. RT3 pretty
much worked out of the box I believe there were one or two things I had
to ignore when I ran test deps. Specifically there is no Apache::Request
that is compatible with Apache 2.0, and at the time there was also no
Apache::DBI.

-Matt

I’m not sure how to ask this delicately, but when do you estimate that a
near final release of 3.0 will be done? I’m several days into setting up
RT2.0 for our needs, but if 3.0 is going to be stable soon, I want to
follow that branch now instead of doing an upgrade in a month.
I understand there probably isn’t a market driven release date like other
software, but I’m looking for some idea so I can make an informed
decision.

It all depends on how the beta series goes. If everything goes smoothly,
I could see 3.0.0 happening in early March. if it doesn’t, well, it’ll
take longer.

�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.