hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14175) Adopt releasedocmaker for better generated release notes
Date Thu, 30 Jul 2015 23:10:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648455#comment-14648455

Andrew Purtell commented on HBASE-14175:

According to Allen, we can generate release notes for all releases in a range to bootstrap:

releasedocmaker.py --license --projecttitle "Apache HBase" --index --project HBASE \
  --range --version 0.98 --version 2.0.0

Could do this by hand, update one of the site sources to point to where the generated relnotes
land, then commit the results. 

In order to make this repeatable for RCs, we'll need to have a Yetus release to consume or
temporarily take releasedocmaker.py into our dev-support/ (the latter being a poor option),
then add the right magic to make_rc.sh and release HOWTO.

> Adopt releasedocmaker for better generated release notes
> --------------------------------------------------------
>                 Key: HBASE-14175
>                 URL: https://issues.apache.org/jira/browse/HBASE-14175
>             Project: HBase
>          Issue Type: Task
>            Reporter: Andrew Purtell
>             Fix For: 2.0.0
> We should consider adopting Hadoop's releasedocmaker for better release notes. This would
pull out text from the JIRA 'release notes' field with clean presentation and is vastly superior
to our current notes, which are simply JIRA's list of issues by fix version. Could hook it
into the site build. A convenient part of Yetus to get up and running with. 

This message was sent by Atlassian JIRA

View raw message