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/... {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.