Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 3 Nov 2015 10:56:27 +0000 (UTC)
From: "Joseph Witt (JIRA)" <jira@apache.org>
To: commits@nifi.apache.org
Message-ID: <JIRA.12909958.1446547193000.135258.1446548187855@Atlassian.JIRA>
In-Reply-To: <JIRA.12909958.1446547193000@Atlassian.JIRA>
References: <JIRA.12909958.1446547193000@Atlassian.JIRA>
 <JIRA.12909958.1446547193458@arcas>
Subject: [jira] [Resolved] (NIFI-1100) Add proper signed release tag for
 releases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/NIFI-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt resolved NIFI-1100.
-------------------------------
    Resolution: Fixed

> Add proper signed release tag for releases
> ------------------------------------------
>
>                 Key: NIFI-1100
>                 URL: https://issues.apache.org/jira/browse/NIFI-1100
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>            Priority: Minor
>             Fix For: 0.4.0
>
>
> A few members of the community have asked that we create a proper signed release tag.  Today our release tags are based on the release candidate.  But this is confusing to others.  For instance the release of nifi-0.3.0 has a tag in Git called 'nifi-0.3.0-RC1'.  This doesn't really help others know that this is what was the actual release.  The RM needs to make a tag called 'nifi-0.3.0' on the passage of the release vote.
> In addition we should sign the release tag (the RM should) so that it is clearly an authoritative tag.  Instructions on how to do this coming shortly.  Also need to add this to our release documentation


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)