There will be a small group set up for the next releases of iMS consisting
of active users (users who know the product and participate).  There will
probably be upgrades of:

2.1
2.5
3.0

That's the initial plan for now (of course, this can change).  At any rate,
we have adopted a new policy that should make things better.  All small
upgrades (from, say, 2.0 to 2.0a) will include only small enhancements or
fixes.  No new features will be included in these small upgrades.  Moderate
feature upgrades will increase the minor version (from, say, 2.0 to 2.1 or
2.5) and major enhancements will be released in a major version change
(version 2.0 to 3.0, for example).  This will allow us to keep track of
versions more easily.

In the next month or so I'll put up additional information for those
interested in the closed beta for the next release.

Regards,

Howie

----- Original Message -----
From: "Tac/Smokescreen Action Network" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Saturday, March 17, 2001 10:32 AM
Subject: Re: [iMS] CF_iMSmonitor


> Sure, absolutely.  Although at this point support my be difficult, because
> there was so much setup involved (it required installing the CFX_Socket
tag
> as well).
>
> Adding support directly in iMS would be relatively easy, I think -- it
just
> opening a socket and writing to it.  Integrating it with 2 CF tags, called
> by iMS, has lots of overhead.
>
> Of course, that would be one more thing that would delay 2.0, which really
> needs to come out.  Maybe 2.1?
>
> Tac



========================================================================
     This list server is Powered by iMS
   'The Swiss Army Knife of Mail Servers'
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================

Reply via email to