You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@yetus.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2015/10/14 05:10:05 UTC

[jira] [Updated] (YETUS-71) releasedocmaker shouldn't use all desc when no release notes field

     [ https://issues.apache.org/jira/browse/YETUS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kengo Seki updated YETUS-71:
----------------------------
    Attachment: YETUS-71.00.patch

I thought the latter is better, because all issues are already listed in CHANGES so subject-only release note is almost meaningless.
Attaching a patch, which includes YETUS-31.01.patch. I'll rebase it once YETUS-31 is committed. I ran this patch applied version for BigTop 1.0.0 and confirmed only BIGTOP-1831 is shown in RELEASENOTES.

> releasedocmaker shouldn't use all desc when no release notes field
> ------------------------------------------------------------------
>
>                 Key: YETUS-71
>                 URL: https://issues.apache.org/jira/browse/YETUS-71
>             Project: Yetus
>          Issue Type: Bug
>          Components: Release Doc Maker
>            Reporter: Allen Wittenauer
>         Attachments: YETUS-71.00.patch
>
>
> It would be better if releasedocmaker limited its use of description fields when release notes support isn't turned on for a given project.  Perhaps only use it if the issue is marked as incompatible and/or important.



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