On 11/03/2013, at 4:25 PM, Daz DeBoer <[email protected]> wrote:
> On 11 March 2013 09:12, Luke Daley <[email protected]> wrote: > >> 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. > > I assume this means that the release notes for the final will also include > information of the known-issues/fixes for each of the RCs? (In fact I'm > pretty sure of it). I think it makes perfect sense to do this, and keep the > release notes generation simple. Yes, you're right. Might be a good opportunity for someone else to dig in to how this works. We also need to improve the way we test this stuff. -- 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
