Jayush Luniya created AMBARI-10289:
--------------------------------------
Summary: 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
Release work for Apache Ambari 2.0.0 RC3 release based on the feedback received
during RC2 voting.
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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
