[BUGFIX] Configuration Tool creates invalid extTables.php file

[Packages/TYPO3.CMS.git] / SVNreadme.txt

diff --git a/SVNreadme.txt b/SVNreadme.txt
index 136d4d2..8171d5e 100644 (file)
--- a/SVNreadme.txt
+++ b/SVNreadme.txt
@@ -1,22 +1,42 @@
-ABOUT GLOBAL EXTENSIONS:
-Starting with version 4.0 of TYPO3 the directory typo3/ext/ is considered locally composed and maintained.
-This means you can put a custom collection of extensions here which you will have to maintain independently of TYPO3core.
-Some of the old global extensions have been moved to be system extensions for your convenience.
-Notice that individual extensions might infact have their own CVS/SVN project somewhere, like on
-SourceForge.net, project "TYPO3 Extension Development Platform" (typo3xdev).
+USING TYPO3 FROM SUBVERSION REPOSITORY
+=======================================

 
 

+About global extensions:
+ Starting with version 4.0 of TYPO3 the directory typo3/ext/ is considered
+ locally composed and maintained. This means you can put a custom
+ collection of extensions here which you will have to maintain
+ independently of TYPO3core. Some of the old global extensions have been
+ moved to be system extensions for your convenience.

 
 

-IMPORTANT POST-CHECKLIST:
-Follow this list IMMEDIATELY after updating sources from SVN (both core and extensions):
-- Update database: In the Install Tool, click "COMPARE" for "Update required tables" in "Database Analysis" section. You might dump the static tables as well, but less likely to be important
-- "Clear temp_CACHED" files from "typo3conf/" of your sites
-- "Clear All Cache"
-- Using PHP-accelerator or other PHP cache? If you fatal PHP-errors, always remove the cached files (eg. "/tmp/phpa_*"), restart Apache and try again.
-(Hint: Take a look at "misc/superadmin.php" script which will greatly help you to maintain multiple TYPO3 installations when updating)
+ Notice that individual extensions might in fact have their own CVS/SVN
+ project somewhere, like on SourceForge.net, project "TYPO3 Extension
+ Development Platform" (typo3xdev).

 
 

+Important post-checklist:
+ Follow this list IMMEDIATELY after updating sources from SVN (both core
+ and extensions):

 
 

-COMMITING CHANGES TO THE CORE:
-This is only allowed for members of the core team (http://typo3.org/teams/core/) who is also having "developer" status on SourceForge (http://sourceforge.net/project/memberlist.php?group_id=20391).
-There is defined a set of rules and conditions under which to commit to the core SVN. These are found in "misc/core_svn_rules.txt
+ - Update database: In the Install Tool, click "COMPARE" for "Update
+   required tables" in "Database Analysis" section. You might dump the
+   static tables as well, but less likely to be important
+ - "Clear temp_CACHED" files from "typo3conf/" of your sites
+ - "Clear FE Cache"
+ - Using PHP-accelerator or other PHP cache? If you fatal PHP-errors,
+   always remove the cached files (eg. "/tmp/phpa_*"), restart Apache and
+   try again.

 
 

-- kasper
+ (Hint: Take a look at "misc/superadmin.php" script which will greatly
+ help you to maintain multiple TYPO3 installations when updating)
+
+Committing changes to the core:
+ This is only allowed for members of the core team [1] who are also having
+ "developer" status on SourceForge [2].
+
+ There is defined a set of rules and conditions under which to commit to
+ the core SVN. These are found in "misc/core_svn_rules.txt".
+
+For more questions, please refer to [3].
+
+[1] http://typo3.org/teams/core/
+[2] http://sourceforge.net/project/memberlist.php?group_id=20391
+[3] http://typo3.org/teams/core/contact/