on 1/15/01 12:36 PM, "Colin Chalmers" <[EMAIL PROTECTED]> wrote:
> In order to avoid the problem of constantly saying "after we do this...we'll
> release" is it beter to make a list and say right "we'll change that and
> that and then we'll go for release 0.5"? That way it may be clearer to all
> who helps with the development work when the release is coming and decide to
> move some other work into a later fase? Priorities?
The problem with that is the list keeps changing. :-)
> I shall be working *a lot* with Turbine this year ;-)) I've committed a
> couple of major projects at my company to Turbine so it's in my best
> interests that it works as well as possible. Unfortunately I always get the
> feeling that I'm one step behind you guys :-( But be rest assured I can run
> fast ;-)) In other words I shall be commting what i can and testing where I
> can.
To be cutting edge, join IRC.
irc.working-dogs.com:6667 #turbine
Jason, Fedor, John, Myself and others generally hash stuff out there and
then post summaries to the list.
> Any pluggable form of interface sounds good to me. I was also considering
> looking into the possibility of some form of JMS/MQseries interfacing.
> Basically because I need it for a project. I'm also in favour of a one
> time make over to get it right for release, but with the view that there is
> an end and a release *very* soon.
I suspect the release will be around JavaOne. That is what I'm pushing for.
I also want to see Velocity released as well.
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
