Hi Jorge,
I don't know if anyone else is working on the 2.4 codebase at the
moment. Personally, I am using CVS head but I have been responsible for
some of the bigger changes since 2.3 so it is easier for me. I would
like to see all the embedded services replaced by fulcrum services
before a release and I suspect that this is not a five minute job. I am
gradually making progress.
Apart from the possible addition of a Fortress service, and moving the
rest of the services to fulcrum components, I don't think that there is
much more to do for a release.
The other work that I am doing is to write additional pluggable services
which can use the framework either as replacement valves or as
additional components. This work is separate from Turbine. As such it is
not part of a 2.4 experiment.
I don't think the roadmap has changed. I was out of action for 3 months
earlier this year, but now I'm back I am actively working towards a
release, However, as always, I have other committments to balance.
Sadly, I cannot put a firm date on when a release might happen. I have
no idea if anyone else is working on this codebase at the moment.
Henning did post something about taking an interest in 2.4, which would
be great.
Peter
Jorge Uriarte wrote:
I'm using Turbine extensively, I don't like using a long deprecated
container like ECM in my applications and will probably write the code
and get as much of fulcrum as I need compatible with Fortress before
deploying my next Turbine application.
If someone hasn't beaten me to it by then, that is ;-)
Excuse my question :-)
Is there any update on the roadmap toward T2.4?
I do remember a thread from some months ago, mainly regarding the choose
of container.
There have been some work in Scarab porting from T3 to T2.4 (Peter
Ledbrook's patchs sent days ago are born from this effort, I guess) ,
and we're using YAAFI for the fulcrum services. We'd like to know if 2.4
is meant to be 'stable' release soon, of it's still an experimental branch.
Thank you very much!
_
Jorge
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
