| Line 28: | Line 28: | ||
http://rev.fckeditor.net/ | http://rev.fckeditor.net/ | ||
| − | The list in the above site is quite similar to the [http://dev.fckeditor.net/log/FCKeditor/trunk|trunk log page], with the exception that it contains and additional column called "Test". A link can be found there to open the sample pages of FCKeditor, generated for each precise revision. | + | The list in the above site is quite similar to the [http://dev.fckeditor.net/log/FCKeditor/trunk| trunk log page], with the exception that it contains and additional column called "Test". A link can be found there to open the sample pages of FCKeditor, generated for each precise revision. |
| + | |||
| + | == Repository Structure == | ||
| + | |||
| + | <pre> | ||
| + | FCKeditor -----------+ Every subproject will have a directory in the root. | ||
| + | trunk -----------+ This is the development place. | ||
| + | branches | ||
| + | developers --+ | ||
| + | features | Isolated development spaces. | ||
| + | versions ----+ | ||
| + | tags | ||
| + | 2.3.2 -------+ | ||
| + | 2.3.1 | A tag will be available for each version release. | ||
| + | 2.3 | It contains the development version (trunk) at release time. | ||
| + | 1.6.1 -------+ | ||
| + | </pre> | ||
| + | All subprojects in the repository will present a structure similar to the above. | ||
| + | |||
| + | === 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). | ||
| + | |||
| + | 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". | ||
Revision as of 11:08, 23 January 2008
Contents
Development SVN
The SVN repository used for the development can be found at (browsable):
The SVN contains the "development version" of FCKeditor. 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 FCKreleaser (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:
- http://www.fckeditor.net/nightly/FCKeditor_N.zip
- http://www.fckeditor.net/nightly/FCKeditor_N.tar.gz
You may also test it online 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.
Working with SVN
Some basic SVN usage information can be found at the SVN Basics page.
Testing Old Revisions
There are occasions during the development, when bugs are introduced by recent changes in the code. To precisely understand and find when things changed, we have created a dedicated web site with a list of all revisions available for the trunk:
The list in the above site is quite similar to the trunk log page, with the exception that it contains and additional column called "Test". A link can be found there to open the sample pages of FCKeditor, generated for each precise revision.
Repository Structure
FCKeditor -----------+ Every subproject will have a directory in the root.
trunk -----------+ This is the development place.
branches
developers --+
features | Isolated development spaces.
versions ----+
tags
2.3.2 -------+
2.3.1 | A tag will be available for each version release.
2.3 | It contains the development version (trunk) at release time.
1.6.1 -------+
All subprojects in the repository will present a structure similar to the above.
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).
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".