@@ -4,7 +4,7 @@ Release criteria
4
4
Ideally, the following minimum criteria should be fulfilled before a new
5
5
final (i.e. non-prerelease) version is released:
6
6
7
- - The code coverage for blocks must be at least 80 %
7
+ - The overall code coverage must be at least 70 %
8
8
- No findbugs warnings
9
9
- No stoppers
10
10
- All bugs and enhancements must be evaluated
@@ -19,7 +19,7 @@ Checklist for releasing OpenGrok:
19
19
20
20
1) sanity check:
21
21
22
- - index
22
+ - index fairly large code base, ideally multiple projects
23
23
- deploy webapp
24
24
- check UI:
25
25
- history view
@@ -30,13 +30,9 @@ Checklist for releasing OpenGrok:
30
30
- check sorting using multiple criteria
31
31
- perform search using multiple fields across multiple projects
32
32
33
- 2) check all tests, tests code coverage:
34
- junit, pmd, findbugs, checkstyle, emma, jdepend
33
+ 2) check all tests pass, test code coverage is above given threshold
35
34
36
- emma reports should be based according to what is set for the release,
37
- usually it's overall coverage above 80%.
38
-
39
- Jenkins can help here.
35
+ Additional tools to use: pmd, findbugs, checkstyle, jdepend
40
36
41
37
The release is OK, once above is fulfilled to our satisfaction.
42
38
@@ -60,4 +56,5 @@ Checklist for releasing OpenGrok:
60
56
of the release, e.g. adding list of issues fixed, whether complete reindex
61
57
is necessary etc.
62
58
63
- 5) Send announcement to
[email protected] , Slack channel etc.
59
+ 5) Send announcement to
[email protected] ,
60
+ the #opengrok Slack channel etc.
0 commit comments