Skip to content

The Unified and Autonomous Development Platform

Add documentation for 5.2.0

Robin Shena56e81bdf272
diff --git a/doc/images/child-projects.png b/doc/images/child-projects.png
new file mode 100644
index 0000000000..3be44f72af
Binary files /dev/null and b/doc/images/child-projects.png differ
diff --git a/doc/incompatibilities.md b/doc/incompatibilities.md
index bee2ba843f..908652b5f3 100644
--- a/doc/incompatibilities.md
+++ b/doc/incompatibilities.md
@@ -1,3 +1,8 @@
+# 5.2.0
+
+1. Job variable *@project_name@* should be replaced by *@project_path@*
+2. Job match condition in job executor is renamed as job requirement, and the criteria to match job name is no longer valid. Executor can now be specified when define the job.
+
# 4.3.0
1. Service definition is separated from job definition. Previous service defined in job will be moved out of job and take the name _\<job name\>-\<service name\>_ to avoid possible name conflicts. You either need to change it back to use original name in case there is no conflicts, or change your build script to use the new service name.
diff --git a/readme.md b/readme.md
index 4db4687495..36f36f9c98 100644
--- a/readme.md
+++ b/readme.md
@@ -97,4 +97,10 @@ The ability to submit and discuss issues over email makes OneDev a perfect custo
Define permission schemes best suiting your development workflow. For instance, you may specify who can change particular source folder, who can assign issues, who can run release builds, or who can access build log, etc.
-![Role](doc/images/role.png)
\ No newline at end of file
+![Role](doc/images/role.png)
+
+### Project Hierarchy and Setting Inheritance
+
+Projects can be organized in a tree structure, and settings of parent project can be inherited by children. This saves a lot of efforts when manage a lot of projects with some common settings.
+
+![Child Projects](doc/images/child-projects.png)
\ No newline at end of file