Hi, thanks to the work of the ASF infrastructure team and especially Henri Yandell and Daniel Rall, the Turbine Source code repository is now officially living at the new location
http://svn.apache.org/repos/asf/jakarta/turbine/ and uses Subversion as its SCM tool. We converted the following repositories: jakarta-turbine-2 (Turbine 2.3 branch and releases, Turbine 2.4 (HEAD) branch) --> turbine/core Turbine 2.4 --> turbine/core/trunk Turbine 2.3 --> turbine/branches/TURBINE_2_3_BRANCH Turbine 2.3 Release --> turbine/core/tags/TURBINE_2_3 Turbine 2.3.1 Release --> turbine/core/tags/TURBINE_2_3_1 Turbine 2.4 M1 Release -> turbine/core/tags/TURBINE_2_4_M1 ... so on. jakarta-turbine-fulcrum (Fulcrum components) --> turbine/fulcrum with the CVS HEAD at turbine/fulcrum/trunk (We might want some discussion whether it is more clever to reorganize this branch into turbine/fulcrum/cache/trunk [...] turbine/fulcrum/factory/trunk [...] turbine/fulcrum/groovy/trunk [...] turbine/fulcrum/yaafi/trunk and so on. It all depends whether it is useful to have the various components to be able to build (and release!) standalone or not. Discussion wanted. jakarta-turbine-stratum --> turbine/stratum with the CVS HEAD at turbine/stratum/trunk Why did we migrate Stratum? Basically, because it is still in use with Turbine-2 and I do intend to make a final 1.0 release and then mothball it. jakarta-turbine-site --> turbine/site without any tags or trunk. This repo is for building the basic turbine site and is of interest mostly for the developers. Please note that we did _not_ migrate the jakarta-turbine-3 tree from CVS. As we consider this tree "dead" and no longer in active development by the core developers but still in use by some projects, we intent to keep it at CVS ATM to allow those that still use T3 to do the odd bug fix. jakarta-turbine-jcs was migrated to jakarta/jcs (this happened accidentially on purpose and was oked by the JCS people. :-) ) The following repositories are now very high on the "endangered species list": jakarta-turbine-component/ Empty and probably without function jakarta-turbine-flux/ The "flux" tool. Current state is unknown, probably obsolete jakarta-turbine-jyve/ Current state unknown. jakarta-turbine-orgami/ Current state unknown. jakarta-turbine-tdk/ No longer any development. jakarta-turbine-torque/ Migrated to db-torque a long time ago. If any of you (users / developers) can give a good reason why we should keep these repos, please speak up now. Else they will go to the Apache Archives. All migrated repos (jakarta-turbine-2, jakarta-turbine-fulcrum, jakarta-turbine-stratum, jakarta-turbine-jcs, jakarta-turbine-site) will be going to the Archives anyway. About the Subversion repos ========================== We migrated the repositories using the cvs2svn tool. On the imports, all files have a property which contains their revision in the CVS trees: e.g. svn propget cvs2svn:cvs-rev turbine-2.3/maven.xml 1.16.2.2 All checked in revisions of all files contain the matching CVS revision from the old repository in this property. There might be a few files / dirs in the repository which have "cvs2svn" as Last Changed Author. These have been created by the conversion itself. If you have any questions about the conversion, feel free to ask on the -dev list. I intend to update the various web sites later this week. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire Linux, Java, perl, Solaris -- Consulting, Training, Development "Now you can start with implementation and integration and do the requirements later". -- Prof. Dr. Dr. h.c. Manfred Broy about the new german federal software development standard "V-Model XT" (found at http://de.biz.yahoo.com/050207/299/4en0t.html) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
