|
⇤ ← Revision 1 as of 2005-03-22 05:44:02
Size: 1221
Comment: missing edit-log entry for this revision
|
← Revision 2 as of 2009-09-20 23:50:23 ⇥
Size: 1212
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''Navigation trail:''' TurbineProjectPages - JakartaTurbine2 - [wiki:/Development Development] - [wiki:/DevelopmentRoadMap Road Map] | '''Navigation trail:''' TurbineProjectPages - JakartaTurbine2 - [[/Development|Development]] - [[/DevelopmentRoadMap|Road Map]] |
| Line 8: | Line 8: |
| * [wiki:TurbineAvalonization Turbine should be able to use avalon components] - Done | * [[TurbineAvalonization|Turbine should be able to use avalon components]] - Done |
Navigation trail: TurbineProjectPages - JakartaTurbine2 - Development - Road Map
Development road map for Turbine > 2.2
Turbine 2.3
- The Services should stay as they are
Turbine should be able to use avalon components - Done
- Torque should be loaded as an avalon component - Done
The Component Service should be able to use Avalon Components. Not the Turbine Service Broker itself. This would be much too heavy. -Henning
- Backporting of services from Fulcrum
- XML-RPC - Done
- Scheduler - Done
- Crypto - Done
- Fileupload - Done
Henning's DB Security Service (will be TorqueSecurityService)
- Release of Fulcrum 1.0 at the same time - (we need fulcrum for the 2.4 release, not for 2.3)
open issues for 2.3
- Should any services from Fulcrum be used by default?
Turbine 2.3+
- The services should be avalon components
- fulcrum or plexus??
- We should decide what will become turbine 3.0!
- Will the current turbine-3 code ever be released?
- Will Plexus/Summit replace the existing Turbine code?
- Yes? when will this happen?