Hi all, We discussed this when we released 1.3, but I dropped the ball and it didn't happen for 1.4. I also can't find any record of us discussing how we want to solve this, but I have a recollection of the discussion.
The core problem is that we don't specify anywhere what the issues were with an RC that caused a subsequent RC. The information is in JIRA, but that's not quite explicit enough. My idea at this stage is to just add some more smarts to the release notes so that we can query JIRA for this info and display it dynamically. We already pull the fixed issues dynamically so there is some precedent for this. Do we need to be sensitive to the exact version that the release notes are being produced for here? If we aren't sensitive to this, the release notes for all RCs would list the known issues for all RCs. This is the simplest thing to do implementation wise. The alternative would be to detect at build time what the exact version is and conditionally include code that checks for issues with RCs. I would prefer to avoid this as I'd like to build the release notes the same way every time. Does anyone object to this approach? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
