[
https://issues.apache.org/jira/browse/HADOOP-11813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504483#comment-14504483
]
Darrell Taylor commented on HADOOP-11813:
-----------------------------------------
There were no tests around this originally, do some need to be written?
Manual steps taken to test this were :
{code}
cd hadoop-common-project/hadoop-common/src/site/markdown/release/
python ../../../../../../dev-support/releasedocmaker.py --version 3.0.0 --index
{code}
Then confirmed that files were produced in
hadoop-common-project/hadoop-common/src/site/markdown/release/3.0.0-SNAPSHOT/.
The CHANGES.3.0.0-SNAPSHOT.md file contained the work 'Unreleased' in this
case. The same command was run again with the --usetoday switch and the
CHANGES.3.0.0-SNAPSHOT.md included today's date instead of 'Unreleased'.
This was also checked through the maven build by running
{code}
mvn pre-site -DskipTests -Preleasedocs
{code}
The CHANGES.3.0.0-SNAPSHOT.md file included today's date instead of
'Unlreleased'
> 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: Task
> Components: build
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Darrell Taylor
> Priority: Minor
> Labels: newbie
> Attachments: 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)
