[
https://issues.apache.org/jira/browse/METRON-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965399#comment-15965399
]
ASF GitHub Bot commented on METRON-845:
---------------------------------------
GitHub user mattf-horton opened a pull request:
https://github.com/apache/incubator-metron/pull/525
METRON-845 Increment build number to 0.4.0
Simply replaced all effective Metron version strings, from "0.3.2" to
"0.4.0".
Used `mvn versions:set -DnewVersion=0.4.0` first, then did
```
for f in `grep -r -l "0\.3\.1" * | egrep -v '^site/'` ; do echo " "; echo
$f; grep "0\.3\.1" $f; done
```
to catch the non-maven files, and hand-edited them.
The remaining handful of .md and log files containing "0.3.2" are not
effective Metron versions, but recordings of previous uses, so they are not
changed.
NOTE: The new branch has not propagated to github, presumably because only
commits stimulate the propagation, and a new branch copied from existing master
is not technically a commit. So we are using this low-risk commit to cause
that propagation, even though it needs a few more hours to run full tests.
## 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] (IN PROCESS) 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] (IN PROCESS) 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:
- [NA] 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/incubator-metron METRON-845
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/525.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 #525
----
commit ad16caf4bca1cdc2a9e573378981c37b29dcce20
Author: mattf-horton <[email protected]>
Date: 2017-04-12T05:02:59Z
METRON-845 Increment build number to 0.4.0
----
> Increment build number to 0.4.0
> -------------------------------
>
> Key: METRON-845
> URL: https://issues.apache.org/jira/browse/METRON-845
> Project: Metron
> Issue Type: Bug
> Reporter: Matt Foley
>
> Since a release candidate build will shortly be underway, increment the
> Metron build version from 0.3.1 to 0.4.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
