forked from malysoun/zenoss-zapp
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrelease_how_to.txt
56 lines (34 loc) · 1.16 KB
/
release_how_to.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
releasing a new version from a snapshot
Check out the master branch and make sure to have latest master
> git checkout master
> git pull origin master
Check out the develop branch
> git checkout develop
<release_name> is usually the next version. e.g., if the version
in develop is "0.0.3-SNAPSHOT" and in master "0.0.2", then the
<release_name> will be the new version in master, "0.0.3".
This will start a new release branch
Make sure you have the latest develop
> git pull origin develop
> git flow release start <release_name>
> mvn versions:set -DnewVersion=0.0.3
Run tests; verify things still work
> mvn versions:commit
Update any docs or release notes
Commit everything
> git commit....
Don't push...
> git flow release finish <release_name>
> git push origin --tags
You will be on the develop branch again.
While on develop branch increment develop branch to the next snapshot
> mvn versions:set -DnewVersion=0.0.4-SNAPSHOT
> mvn versions:commit
Verify tests etc...
check in develop version bump...
> git commit...
push your develop branch
> git push
push the master branch which should have the new released version
> git checkout master
> git push