ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10289) Release work for Apache Ambari Release 2.0.0 RC3
Date Mon, 30 Mar 2015 22:43:53 GMT

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

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

1. Let's do "mvn versions:set" to 2.0.0 and grep for "-SNAPSHOT" to make sure we don't have
SNAPSHOT references.  Commit the changes to branch-2.0.0.  Update the how to release wiki
accordingly.
2. Remove the DISCLAIMER file from branch-2.0.0 and trunk.
3. Rename the artifact to apache-ambari-[version]-src.*.  Update the how to release wiki accordingly.
4. Rename the .sha extension to .sha1.  Update the how to release wiki accordingly.
5. [~jluniya] needs to add his key to the KEYS file.  
6. Push the KEYS file to https://dist.apache.org/repos/dist/release/ambari/
7. Publish ambari-views.jar and the parent poms to Maven.  [~u39kun] to take care of that.
8. Look into CHANGES.txt, dist dev, and other best practices for future releases.


> 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.
> 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