alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

Clarifying that each issue should be assigned to a component

Browse Source
This commit is contained in:
Gunnar Morling 2017-11-15 20:23:42 +01:00 committed by GitHub
parent d211b0bde5
commit 0565b356d6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
RELEASING.md
View File

@ -3,11 +3,14 @@
The Debezium project uses Maven for its build system, relying up on the _release_ plugin to most of the work. This document describes the steps required to perform a release.
## Verify Jira issues
All issues planned for this release must be resolved. If not they have to either be re-planned to another release or rejected. Use JQL query to find offending issues
All issues planned for this release must be resolved. If not, they have to either be re-planned to another release or rejected. Use JQL query to find offending issues
```
project=DBZ AND fixVersion=<VERSION> AND status NOT IN ('Resolved', 'Closed')
```
Also make sure that each issue is assigned to a component ("mysql-connector" etc.).
## Update the changelog
The change log should be updated with all relevant info on new features, bug fixes and breaking changes.