Changes between Version 22 and Version 23 of SVN

Timestamp:

Jun 30, 2010, 9:59:32 AM (14 years ago)

Author:

Frederico Caldeira Knabben

Comment:

--

SVN

@@ -4 +4 @@
 
 The SVN repository used for the development can be found at ([/browser browsable]):[[BR]]
-http://svn.fckeditor.net
+http://svn.ckeditor.com
 
 The SVN contains the "development version" of CKEditor. It doesn't reflect the contents of public distributions. Actually, some files are not present in the public downloads (like the "_dev" folder or the compressed "js" files, for example). 
 
-'''We don't recommend using this version on production'''. There are also security implications on doing so. To make the SVN version "production safe", it must be processed with CKreleaser (available inside _dev). A safer and easier option is to simply use the Nightly Build, which is already processed.
+'''We don't recommend using this version on production'''. There are also security implications on doing so. To make the SVN version "production safe", it must be processed with CKReleaser (available inside _dev). A safer and easier option is to simply use the Nightly Build, which is already processed.
 
 == Nightly Build ==
 
-Every night, at 0:30 PST, a "'''Nightly Build'''" is generated, from the SVN version. You may download it from one of the following links:
+Every night, at 0:30 PST, a "'''Nightly Build'''" is generated, from the SVN version. Visit the following web site to download it:[[BR]]
+http://nightly.ckeditor.com/
 
- * http://download.cksource.com/CKEditor/CKEditor/Nightly%20Build/ckeditor_nightly.zip
- * http://download.cksource.com/CKEditor/CKEditor/Nightly%20Build/ckeditor_nightly.tar.gz
-
-You may also test it online [http://nightly.ckeditor.com/demo here].
+You may also test the nightly online directly [http://nightly.ckeditor.com/demo here].
 
 The nightly is processed for public distribution. As the fixes and features available on nightlies are still under testing and development, it may be used on production systems at your own risk.
@@ -53 +51 @@
 === The "trunk" ===
 
-The trunk is the effective place we'll be working everyday. Usually we'll have local working copies of the trunk only (and possibly any branch).
+The trunk is the effective place we'll be working everyday. Usually we'll have local working copies of the trunk only (and possibly some branches).
 
 Starting from version 2.4, the trunk will always have stable code which we can publish to the public SVN, and eventually release officially. So, only important bugs and small changes will be committed here, while more delicate and extensive developments will be done in a "branch".
@@ -75 +73 @@
 When '''merging branches to the trunk''', first merge the trunk to the branch and check that everything is ok. Make the necessary changes and commit the branch. Then switch to the trunk and merge the differences between the branch HEAD and the last trunk revision you have just merged to the branch (usually HEAD). Then, if the branch is not anymore needed, just delete it (SVN delete I mean).
 
-If you are insecure, don't be afraid of asking others to execute this task for you.
+If you are unsure, don't be afraid of asking others to execute this task for you.
 
 TortoiseSVN offers a nice tool to track the creation an life-cicle of branches. It is called "Revision graph". The SVN log can also be used for it.
@@ -87 +85 @@
 Try to make a single commit for each fix or feature. Avoid making big commits with lots of changes. This separation makes each commit an isolate thing. It makes code review and merge tasks easy.
 
-The commit log message is very important. Don't underestimate it. It must be well written and informative. Whenever possible, make references to related trac items, like tickets or changesets. You may use one of the "standard" messages, like the following examples:
+The commit log message is very important. Don't underestimate it. It must be well written and informative. Whenever possible, make references to related Trac items, like tickets or changesets. You may use one of the "standard" messages, like the following examples:
 
- * Fixed #81: IE has a DOM bug that caused FCKDomTools.RTrimNode to break. 
- * Merged trunk r131:132 into branches/versions/2.4.x
- * FCKeditor 2.4 tagging
+ * #81: IE has a DOM bug that caused FCKDomTools.RTrimNode to break. 
+ * Merged trunk r131:132 into branches/versions/2.4.x.
+ * CKEditor 3.2 tagging.
 
 == Links ==
 
-'''TortoiseSVN''': the SVN integration with the Windows Shell. This is the best way to work with SVN in Windows:[[BR]]
+'''TortoiseSVN''': the SVN integration with the Windows Shell. This is the best way to work with SVN on Windows:[[BR]]
 http://tortoisesvn.tigris.org/