hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11813) releasedocmaker.py should use today's date instead of unreleased
Date Thu, 07 May 2015 14:38:03 GMT

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

Hudson commented on HADOOP-11813:
---------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #177 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/177/])
HADOOP-11813. releasedocmaker.py should use today's date instead of unreleased (Darrell Taylor
via aw) (aw: rev f325522c1423f89dced999a16d49a004b2879743)
* dev-support/releasedocmaker.py
* hadoop-common-project/hadoop-common/pom.xml
* hadoop-common-project/hadoop-common/CHANGES.txt


> releasedocmaker.py should use today's date instead of unreleased
> ----------------------------------------------------------------
>
>                 Key: HADOOP-11813
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11813
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.0.0
>            Reporter: Allen Wittenauer
>            Assignee: Darrell Taylor
>            Priority: Minor
>              Labels: newbie
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-11813.001.patch, HADOOP-11813.patch
>
>
> After discussing with a few folks, it'd be more convenient if releasedocmaker used the
current date rather than unreleased when processing a version that JIRA hasn't declared released.



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

Mime
View raw message