ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10289) Release work for Apache Ambari Release 2.0.0 RC3
Date Tue, 30 Jun 2015 14:04:06 GMT

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

Hudson commented on AMBARI-10289:
---------------------------------

ABORTED: Integrated in Ambari-branch-2.0.0 #122 (See [https://builds.apache.org/job/Ambari-branch-2.0.0/122/])
AMBARI-10289: Release work for Apache Ambari Release 2.0.0 RC3 (jluniya) (jluniya: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=425d8afc7513f30f958932e344226bb4354899b1)
* contrib/views/capacity-scheduler/pom.xml
* ambari-shell/ambari-python-shell/pom.xml
* ambari-web/pom.xml
* ambari-metrics/ambari-metrics-host-monitoring/pom.xml
* ambari-metrics/ambari-metrics-flume-sink/pom.xml
* ambari-metrics/ambari-metrics-hadoop-sink/pom.xml
* contrib/views/hive/pom.xml
* ambari-shell/ambari-groovy-shell/pom.xml
* pom.xml
* contrib/views/slider/pom.xml
* ambari-client/pom.xml
* contrib/views/files/pom.xml
* contrib/views/pom.xml
* ambari-shell/pom.xml
* ambari-metrics/ambari-metrics-common/pom.xml
* ambari-client/python-client/pom.xml
* ambari-server/pom.xml
* contrib/ambari-scom/pom.xml
* ambari-views/pom.xml
* ambari-metrics/ambari-metrics-kafka-sink/pom.xml
* ambari-views/examples/property-validator-view/pom.xml
* DISCLAIMER.txt
* docs/pom.xml
* ambari-agent/pom.xml
* ambari-project/pom.xml
* ambari-metrics/pom.xml
* ambari-metrics/ambari-metrics-timelineservice/pom.xml
* contrib/ambari-scom/metrics-sink/pom.xml
* contrib/views/jobs/pom.xml
* ambari-metrics/ambari-metrics-assembly/pom.xml
* ambari-admin/pom.xml
* contrib/ambari-log4j/pom.xml
* ambari-metrics/ambari-metrics-storm-sink/pom.xml
* contrib/views/tez/pom.xml
* ambari-client/groovy-client/pom.xml
* KEYS
* contrib/ambari-scom/ambari-scom-server/pom.xml
* contrib/views/pig/pom.xml


> 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 received during
RC2 voting.
> From [~hitesh]
> {quote}
> The pom.xml in https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=log;h=refs/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 time this was fixed.
> No CHANGES.txt or release notes in the release artifact?
> Release artifacts should ideally be named apache-ambari-*. Should the artifact be named
*-src-* too ?
> sha file is named “.sha” but actually contains a sha1 sig.
> The release manager’s keys are not in the KEYS file.
> For future releases, you should really use dist for staging a release. Easier 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. Have those steps been missed again?
> {quote}



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

Mime
View raw message