[jbosstools-issues] [JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936500#comment-12936500 ] 

Michelle Murray commented on JBIDE-16355:
-----------------------------------------

Not to complicate the jira as it is about sourceforge, but in response to Max's comment about jira query links in JBDS documentation:
* The reason not to use a link like nick's [1] in JBDS documentation is that it contains all of the bugs resulting from internal incremental builds that users do not need to know about.
* The jira provided in documentation is limited to bugs only as new features/enhancements are covered in more detail in their own section of the doc.
* It is simpler from a users' perspective to be provided with a ready made query than being told how to build their own.

[1] https://issues.jboss.org/secure/ConfigureReport.jspa?versions=12321748&versions=12322382&versions=12322381&versions=12322380&versions=12322379&sections=all&style=none&selectedProjectId=10020&reportKey=org.jboss.labs.jira.plugin.release-notes-report-plugin%3Areleasenotes&Next=Next
                
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-16355
>                 URL: https://issues.jboss.org/browse/JBIDE-16355
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.2.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/zz_Release_Notes_4.2.0.Alpha1.readme.html/download
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira