This repository was archived by the owner on Aug 20, 2025. It is now read-only.
METRON-1021 increment metron version number to 0.4.1 in poms etc #637
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
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?
Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:
[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?
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: