[rt-users] questions before i install

[Mark D. Anderson]

i'm about to install rt; before i dive in, some questions:

1. the downloaded rt.tar.gz is version 1.0.3; i see commit message regarding 1.3.12, and i see discussion of 2.0
I assume that "2.0" is what 1.3.x will become?

2. i assume that when 2.0 comes out, there will be upgrade scripts from the database in version1.0.3.
but if i install the 1.3.x from cvs (not to mention the twort from sourceforge), i presume there might
*not* be scripts to automatically upgrade my database to be compatible with the final 2.0 version?
so if i do put a 1.3.x snapshot into production, i might be setting myself up for writing some custom sql
later on?

3. there is little information on the sourceforge site about twort. judging from the cvs dates,
there have been checkins there, but there is no information i can find indicating how it compares
to the fsck cvs archive. Also, neither twort nor fsck seems to have a cvs snapshot available;
i don't feel like playing "do i feel lucky" and downloading whatever the latest cvs happens to be,
even if i did want to try 1.3.x instead of 1.0.3.

4. i'm kind of mystified by the various rt email aliases, even after reading the README, fax, and user guide.
There is the "rt mail alias", which would typically be "rt".
Then there is the "default" or "primary" queue, which i guess would be something like "rt-general",
and others for each other queue ("rt-helpdesk", "rt-office", etc.).
Then there are optional email aliases for actions, which i guess have to be per-queue, something
like "rt-general-action", etc. -- if i choose to continue the convention of starting each with "rt-".
But when does email originate from the "rt mail alias" (typically "rt"), rather than from a queue?
When would users send email directly to "rt" rather than to "rt-$queuename"?
Why does there even have to be a user named "rt"? (assuming i have some other user to
run my httpd and to login to mysql).

5. i also couldn't find a clear explanation of "correspond" vs. "comment".

6. is there any revised ETA for a 2.0 alpha?

-mda