[
https://issues.apache.org/jira/browse/NIFIREG-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330876#comment-16330876
]
ASF GitHub Bot commented on NIFIREG-121:
----------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/90
NIFIREG-121 Bumping pom versions from 0.1.1-SNAPSHOT to 0.2.0-SNAPSHOT
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-121
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/90.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 #90
----
commit e00dead2ee3c6a3f8d589625dd8f25456eb65c0f
Author: Bryan Bende <bbende@...>
Date: 2018-01-18T18:00:50Z
NIFIREG-121 Bumping pom versions from 0.1.1-SNAPSHOT to 0.2.0-SNAPSHOT
----
> Bump pom versions to 0.2.0-SNAPSHOT
> -----------------------------------
>
> Key: NIFIREG-121
> URL: https://issues.apache.org/jira/browse/NIFIREG-121
> Project: NiFi Registry
> Issue Type: Task
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.2.0
>
>
> In order to avoid confusion and stay in sync with JIRA, we should set the
> poms on master to 0.2.0-SNAPSHOT.
> If we need to do an 0.1.1 release we can branch off the 0.1.0 release and
> pull in whatever is needed there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
