[Rt-devel] ANNOUNCE AssetTracker 1.0.0rc2

[Todd Chapman]

Sorry, not at this point. Mostly it looks like RT, but with an
Assets menu below the Tickets menu. :)

It's not hard to set up a development RT using SQLite...

-Todd

On Fri, Apr 01, 2005 at 01:01:22PM +1000, Matthew Watson wrote:
> Do you have a demo version of this? I'd like to have a look at it before
> actually nailing it into our installation :)
> 
> Regards,
> Matt.
> 
> 
> > -----Original Message-----
> > From: rt-devel-bounces at lists.bestpractical.com [mailto:rt-devel-
> > bounces at lists.bestpractical.com] On Behalf Of Todd Chapman
> > Sent: Friday, April 01, 2005 10:58 AM
> > To: rt-devel at bestpractical.com
> > Subject: [Rt-devel] ANNOUNCE AssetTracker 1.0.0rc2
> > 
> > The second release candidate of AssetTracker (AT) is
> > now available. (RC1 never saw the light of day.)
> > 
> > SQLite support has been added. Contributed schemas
> > for Postgres and Oracle have been provided, but have
> > not been tested by the AT author.
> > 
> > At this point I would personally use AT in production
> > but that's not a very large testing sample. Please
> > back up your RT before taking the plunge.
> > 
> > Useful links:
> > 
> > http://atwiki.chaka.net/index.cgi?HomePage
> > http://atwiki.chaka.net/at-1.0.0rc2.tar.gz
> > http://atwiki.chaka.net/index.cgi?README
> > 
> > -Todd
> > 
> > _______________________________________________
> > Rt-devel mailing list
> > Rt-devel at lists.bestpractical.com
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> 
> This email and any files transmitted with it are confidential and intended solely for the 
> use of the individual or entity to whom they are addressed. Please notify the sender 
> immediately by email if you have received this email by mistake and delete this email 
> from your system. Please note that any views or opinions presented in this email are solely
>  those of the author and do not necessarily represent those of the organisation. 
> Finally, the recipient should check this email and any attachments for the presence of 
> viruses. The organisation accepts no liability for any damage caused by any virus 
> transmitted by this email. 
>