Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 31 Mar 2015 21:29:54 +0000 (UTC)
From: "Yusaku Sako (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12786856.1427754441000.86328.1427837394574@Atlassian.JIRA>
In-Reply-To: <JIRA.12786856.1427754441000@Atlassian.JIRA>
References: <JIRA.12786856.1427754441000@Atlassian.JIRA>
 <JIRA.12786856.1427754441906@arcas>
Subject: [jira] [Commented] (AMBARI-10289) Release work for Apache Ambari
 Release 2.0.0 RC3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMBARI-10289?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14=
389454#comment-14389454 ]=20

Yusaku Sako commented on AMBARI-10289:
--------------------------------------

+1 for the patch.

> Release work for Apache Ambari Release 2.0.0 RC3
> ------------------------------------------------
>
>                 Key: AMBARI-10289
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10289
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10289.branch-2.0.0.patch, AMBARI-10289.trunk.=
patch
>
>
> Release work for Apache Ambari 2.0.0 RC3 release based on the feedback re=
ceived during RC2 voting.
> From [~hitesh]
> {quote}
> The pom.xml in https://git-wip-us.apache.org/repos/asf?p=3Dambari.git;a=
=3Dlog;h=3Drefs/tags/release-2.0.0-rc2 has a snapshot version.
> The source tarball also has 2.0.0-SNAPSHOT. Various bits of code ( views =
) also have snapshot versions.
> Release contains a DISCLAIMER saying Ambari is still incubating. High tim=
e this was fixed.
> No CHANGES.txt or release notes in the release artifact?
> Release artifacts should ideally be named apache-ambari-*. Should the art=
ifact be named *-src-* too ?
> sha file is named =E2=80=9C.sha=E2=80=9D but actually contains a sha1 sig=
.
> The release manager=E2=80=99s keys are not in the KEYS file.
> For future releases, you should really use dist for staging a release. Ea=
sier to have track and have history on what is being voted on.
> Likewise, the KEYS file should also be available on the download link for=
 users to be able to verify the authenticity of the release.
> I remember there being a problem the last time around where the api jars =
were not deployed to nexus and verified as part of the release process. Hav=
e those steps been missed again?
> {quote}


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