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: development/releasing.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,17 +4,19 @@ With every build, the build process on Travis updates files with an appropriate
4
4
This step is performed, to confirm that the update of versions works properly.
5
5
6
6
To create a release:
7
-
- create release branch and wait for release build to complete successfully
8
-
- merge release branch to master and wait for master build to complete successfully
9
-
- create a release from the master branch using github web page and populate release description using information found on the issues and pull requests for release
7
+
- create release branch from development branch and make sure to name the release branch: `release/vX.Y.Z`
8
+
- update, commit and push at least one file change in the release branch, to kickoff a Travis build
9
+
- wait for th build to complete successfully
10
+
- merge the release branch to master and wait for master build to complete successfully
11
+
- create a release from the master branch using [github releases page](https://github.com/utPLSQL/utPLSQL/releases) and populate release description using information found on the issues and pull requests since previous release.
12
+
To find issues closed after certain date use [advanced filters](https://help.github.com/articles/searching-issues-and-pull-requests/#search-by-open-or-closed-state)
10
13
11
14
The following will happen:
12
-
- build executed on branch `release/v1.2.3-[something]` updates files `sonar-project.properties`, `VERSION` with project version derived from the release branch name
15
+
- build executed on branch `release/vX.Y.Z-[something]` updates files `sonar-project.properties`, `VERSION` with project version derived from the release branch name
13
16
- changes to those two files are committed and pushed back to release branch by Travis
14
17
- when a release is created, a new tag is added in on the repository and a tag build is executed
15
18
- the documentation for new release is published on `utplsql.github.io` and installation archives are added to the tag.
16
19
17
20
Note:
18
-
The released version does not provide access to un-versioned source files (the default zip file from GitHub is empty).
19
21
The sources for release are provided in separate zip files delivered from the Travis build process.
20
-
This is because we do not keep version in our source files in develop branch.
22
+
The built zip files include HTML documentation generated from MD files.
0 commit comments