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

Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2015/12/10 13:38:11 UTC

[jira] [Commented] (QPID-6941) [Website] Automates exporting of release JIRAs into release notes

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

Justin Ross commented on QPID-6941:
-----------------------------------

It already intends to do this, and it does it for me.  How did you invoke the release generation script?  I think you may need to use the ISSUES_RELEASE override (with qpid-java-6.0) to get the right release key into the query.

http://svn.apache.org/repos/asf/qpid/site/README (the part about ISSUES_RELEASE)
http://svn.apache.org/repos/asf/qpid/site/python/generate.py (_fetch_issues)


> [Website] Automates exporting of release JIRAs into release notes
> -----------------------------------------------------------------
>
>                 Key: QPID-6941
>                 URL: https://issues.apache.org/jira/browse/QPID-6941
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Website
>            Reporter: Alex Rudyy
>
> On performing 6.0.0 release, I had to export manually JIRAs from the JIRA system and add them into a release notes template (release_notes.md). IMHO, this step can be automated by adding a function into site generation scripts to call JIRA REST API to extract the release JIRAs and add building JIRAs table in the release template.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org