[jira] [Commented] (METRON-1021) increment metron version number to 0.4.1 in poms etc

["Matt Foley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077363#comment-16077363 ] 

Matt Foley commented on METRON-1021:
------------------------------------

For future reference, the following files had version numbers to change:
{code}
metron-analytics/metron-maas-common/pom.xml
metron-analytics/metron-maas-service/pom.xml
metron-analytics/metron-profiler-client/README.md
metron-analytics/metron-profiler-client/pom.xml
metron-analytics/metron-profiler-common/pom.xml
metron-analytics/metron-profiler/pom.xml
metron-analytics/metron-statistics/pom.xml
metron-analytics/pom.xml
metron-deployment/Kerberos-manual-setup.md
metron-deployment/amazon-ec2/conf/defaults.yml
metron-deployment/inventory/full-dev-platform/group_vars/all
metron-deployment/inventory/quick-dev-platform/group_vars/all
metron-deployment/packaging/ambari/metron-mpack/pom.xml
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/mpack.json
metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
metron-deployment/packaging/docker/rpm-docker/pom.xml
metron-deployment/playbooks/docker_probe_install.yml
metron-deployment/pom.xml
metron-deployment/roles/ambari_master/defaults/main.yml
metron-deployment/roles/ambari_master/tasks/main.yml
metron-deployment/roles/metron_pcapservice/defaults/main.yml
metron-docker/pom.xml
metron-interface/metron-config/package.json
metron-interface/metron-config/pom.xml
metron-interface/metron-config/scripts/package.json
metron-interface/metron-rest-client/pom.xml
metron-interface/metron-rest/pom.xml
metron-interface/metron-rest/src/main/resources/application.yml
metron-interface/pom.xml
metron-platform/README.md
metron-platform/elasticsearch-shaded/pom.xml
metron-platform/metron-api/pom.xml
metron-platform/metron-common/pom.xml
metron-platform/metron-data-management/pom.xml
metron-platform/metron-elasticsearch/pom.xml
metron-platform/metron-enrichment/pom.xml
metron-platform/metron-hbase/pom.xml
metron-platform/metron-indexing/pom.xml
metron-platform/metron-integration-test/pom.xml
metron-platform/metron-management/pom.xml
metron-platform/metron-parsers/pom.xml
metron-platform/metron-pcap-backend/pom.xml
metron-platform/metron-pcap-backend/src/main/scripts/pcap_zeppelin_run.sh
metron-platform/metron-pcap/pom.xml
metron-platform/metron-solr/pom.xml
metron-platform/metron-storm-kafka-override/pom.xml
metron-platform/metron-storm-kafka/pom.xml
metron-platform/metron-test-utilities/pom.xml
metron-platform/metron-writer/pom.xml
metron-platform/pom.xml
metron-stellar/pom.xml
metron-stellar/stellar-common/3rdPartyStellar.md
metron-stellar/stellar-common/README.md
metron-stellar/stellar-common/pom.xml
pom.xml
site-book/pom.xml
{code}

> 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)