[
https://issues.apache.org/jira/browse/METRON-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077383#comment-16077383
]
ASF GitHub Bot commented on METRON-1021:
----------------------------------------
GitHub user mattf-horton opened a pull request:
https://github.com/apache/metron/pull/637
METRON-1021 increment metron version number to 0.4.1 in poms etc
## Contributor Comments
Consistent with proposed post-release actions, incrementing the minor
release number to 0.4.1, so that going forward, builds with additional commits
cannot be mistaken for the recently released 0.4.0 release.
I built, ran all tests, and brought it up briefly in full-dev. Seems okay.
Artifacts have appropriate version numbers.
## Pull Request Checklist
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [NA] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [NA] Have you included steps or a guide to how the change may be verified
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been
executed in the root incubating-metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [NA] Have you written or updated unit tests and or integration tests to
verify your changes?
- [NA] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in
which it is rendered by building and verifying the site-book?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf-horton/metron METRON-1021
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/637.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #637
----
commit c8c04e70266f51c042e72f592598d572edb8bf21
Author: mattf-horton <[email protected]>
Date: 2017-07-06T23:42:46Z
METRON-1021 increment metron version number to 0.4.1 in poms etc
----
> increment metron version number to 0.4.1 in poms etc
> ----------------------------------------------------
>
> Key: METRON-1021
> URL: https://issues.apache.org/jira/browse/METRON-1021
> Project: Metron
> Issue Type: Task
> Reporter: Matt Foley
> Assignee: Matt Foley
>
> It is good practice to increment the build version in POMs immediately after
> a release, so that builds with new stuff cannot be mistaken for builds of the
> release version. Consistent with METRON-1020 I suggest incrementing the minor
> rather than the major version number for now, before we know what we're going
> to release next and when.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
