diff options
| author | G. Ann Campbell <ann.campbell@sonarsource.com> | 2018-08-22 07:51:05 -0400 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2018-08-22 20:21:23 +0200 |
| commit | 53dd61f4cf58190b0a0182def92c7ef5c692d633 (patch) | |
| tree | 4b7ee983e273f0b8256224156a0ffab77a57c90e /server/sonar-docs/src/pages/branches | |
| parent | facddc67e65ce303e40e494d921a53446277cd43 (diff) | |
| download | sonarqube-53dd61f4cf58190b0a0182def92c7ef5c692d633.tar.gz sonarqube-53dd61f4cf58190b0a0182def92c7ef5c692d633.zip | |
SONAR-10576: Use 'New Code Period' in docs
Diffstat (limited to 'server/sonar-docs/src/pages/branches')
| -rw-r--r-- | server/sonar-docs/src/pages/branches/index.md | 4 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/branches/long-lived-branches.md | 4 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/branches/short-lived-branches.md | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/server/sonar-docs/src/pages/branches/index.md b/server/sonar-docs/src/pages/branches/index.md index e5fa3afb4db..76cd3c02f97 100644 --- a/server/sonar-docs/src/pages/branches/index.md +++ b/server/sonar-docs/src/pages/branches/index.md @@ -25,8 +25,8 @@ This corresponds to Pull/Merge Requests or Feature Branches. This kind of branch * will disappear quickly * will be merged rapidly to prevent integration issues * is developed for a given version, so the version does not change, - and there is no Leak Period concept as such; it's all leak period - tracks all the new issues related to the code that changed on it. + and there is no New Code period concept as such; it's all new code +* tracks all the new issues related to the code that changed on it.  diff --git a/server/sonar-docs/src/pages/branches/long-lived-branches.md b/server/sonar-docs/src/pages/branches/long-lived-branches.md index 010edc13b9c..b806d2b6a21 100644 --- a/server/sonar-docs/src/pages/branches/long-lived-branches.md +++ b/server/sonar-docs/src/pages/branches/long-lived-branches.md @@ -18,9 +18,9 @@ During the **first analysis only**, issues (type, severity, status, assignee, ch Then, at each subsequent analysis of the long-lived branch, any new issue that comes from a short-lived branch automatically inherits the attributes (type, severity, ...) the issue had in the short-lived branch. A comment is added to the change log of the issue on the long-lived branch: "The issue had been copied from branch 'the short-live branch' to branch yyy". -## Leak Period +## New Code Period -Because long-lived branches will persist for a long time, you are likely to develop and release multiple versions from it, and so you can change the Leak Period of a long-lived branch in **Administration > Branches**. +Because long-lived branches will persist for a long time, you are likely to develop and release multiple versions from it, and so you can change the New Code period of a long-lived branch in **Administration > Branches**. ## Settings and Quality Profiles on Branches diff --git a/server/sonar-docs/src/pages/branches/short-lived-branches.md b/server/sonar-docs/src/pages/branches/short-lived-branches.md index 1fecddd78c9..d84f56a0ba0 100644 --- a/server/sonar-docs/src/pages/branches/short-lived-branches.md +++ b/server/sonar-docs/src/pages/branches/short-lived-branches.md @@ -27,9 +27,9 @@ The issues visible on the short-lived branch are the new issues corresponding to Modified files are determined based on the checksum of each file on the sonar.branch.target and the short-lived branch. -## Leak Period +## New Code Period -The ephemeral nature of short-lived branches means no explicit Leak Period is necessary; it's all new code. Thus, no "new code" data is available for a short-lived branch. +The ephemeral nature of short-lived branches means no explicit New Code Period is necessary; it's all new code. ## Settings and Quality Profiles on Branches |