You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BRANCHING-MODEL.md
+8-12Lines changed: 8 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,20 +3,16 @@ This section describes
3
3
- how branches are handled
4
4
- defectdojo release cycle
5
5
6
+
Please be careful to submit your pull requests to the correct branch:
7
+
- bugfix: latest "release/a.b.x" branch (+ merge using a separate PR against the dev branch)
8
+
- evolutions: dev branch
9
+
10
+
If in doubt please use dev branch.
11
+
6
12
# Release and hotfix model
7
13

8
-
## Releasing
9
-
- Start a release/x.y.0 release branch off dev branch
10
-
- Commit only bug fixes from `dev` branch onto this branch
11
-
- Dev branch keeps living with further evolutions
12
-
- Every 4-8 weeks, merge the release branch to master and tag x.y.0: this is when the new release is out: x.(y+1).0
13
-
14
-
# Issuing a hotfix
15
-
- In case of major issue found after releasing, and fixed in `dev`:
16
-
- Issue a hotfix branch (first is x.y.1) holding this fix
17
-
- Merge to `master` and the next release branch
18
14
19
15
20
-
Diagrams created with https://www.planttext.com
16
+
Diagrams created with https://www.planttext.com/
21
17
22
-
This model is close to gitflow https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow,https://nvie.com/posts/a-successful-git-branching-model/ with the feature branch being made in each contributor repository.
18
+
This model is inspired byhttps://nvie.com/posts/a-successful-git-branching-model/ with the feature branch being made in each contributor repository.
# Enable prefork and options below to ramp-up celeryworker performance. Presets should work fine for a machine with 8GB of RAM, while still leaving room.
109
+
# See https://docs.celeryproject.org/en/stable/userguide/workers.html#id12 for more details
Copy file name to clipboardExpand all lines: PULL_REQUEST_TEMPLATE.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,16 @@
1
1
This template is for your information. Please clear everything when submitting your pull request.
2
2
3
-
**Note: DefectDojo is now on Python3.6 and Django 2.2.x. Please submit your pull requests to the 'dev' branch as the 'legacy-python2.7' branch is only for bug fixes. Any new features submitted to the legacy branch will be ignored and closed.**
3
+
**Note: DefectDojo is now on Python3.6 and Django 2.2.x.**
4
+
5
+
**Please submit your pull requests to :**
6
+
7
+
**- evolutions: dev branch**
8
+
9
+
**- bugfix: latest "release/x.y.z" branch**
10
+
11
+
**- hotfixes: master branch**
12
+
13
+
If in doubt you can use dev branch, it will just roll-out later.
4
14
5
15
When submitting a pull request, please make sure you have completed the following checklist:
0 commit comments