You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by mp...@apache.org on 2001/12/11 14:33:00 UTC

cvs commit: jakarta-turbine-site/xdocs index.xml

mpoeschl    01/12/11 05:33:00

  Modified:    xdocs    index.xml
  Log:
  add current status to the frontpage
  
  Revision  Changes    Path
  1.5       +22 -2     jakarta-turbine-site/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-site/xdocs/index.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- index.xml	2001/11/17 22:41:14	1.4
  +++ index.xml	2001/12/11 13:33:00	1.5
  @@ -37,19 +37,39 @@
     <p>
       <strong>Turbine 2.1</strong>. Turbine 2.1 is the current
       production quality release.
  -  </p> 
  +  </p>
   
     <p>
       <strong>Turbine 2.2</strong>. Turbine 2.2.x will be the next
       official release. It will include some new features and bug fixes.
  -  </p> 
  +  </p>
   
     <p>
       <strong>Turbine 3.0</strong>.  Turbine 3.x is the development
       tree, has <strong>not been scheduled for release</strong>, and is
       not (yet) recommended for use in a production environment.
     </p>
  +</section>
   
  +<section name="Turbine Status">
  +  <p>
  +    Torque (persistence layer) and Fulcrum (service framework) were decoupled
  +    from Turbine and have there own cvs repositories now.
  +  </p>
  +  <p>
  +    Additions will be made to the 2.2 and 3.0 sources so that Torque and Fulcrum
  +    will be pluggable subsystems so that 2.2 users and 3.0 users can take
  +    advantage of the decoupled Torque and Fulcrum.
  +  </p>
  +  <p>
  +    At this point all versions of Turbine will be able to use the decoupled
  +    Torque and Fulcrum. Everything will work as expected for people using the
  +    old Torque and Fulcrum but development will stop and people will be strongly
  +    encourage to migrate. A migrator will be provided. For Torque a regeneration
  +    of your OM classes should do the trick but the migrator should take care of
  +    the rest. Moving services over to Fulcrum will definitely require the
  +    migrator.
  +  </p>
   </section>
   
   </body>
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>