On 02/09/2013, at 4:11 AM, Daz DeBoer <darrell.deb...@gradleware.com> wrote:
> G'day > > Gradle 1.8 will have some form of support for compiling C and assembling > Assembly into a native binary. I'm currently unsure as to what form that > should take. The issues are: > > 1) I've been quite remiss in getting the documentation and release notes up > to scratch: currently these features are not mentioned at all. I could > definitely get this done this week if prioritised. > > 2) I've recently improved the API for compiler/assembler settings so they are > more cleanly separated per input language. Together with this I've done a > bunch of cleanups / refactorings to this functionality. > > My question is how I should try to incorporate things into Gradle 1.8, which > has already been branched. Options are: > > 1) Push as much as possible on the release branch, in the hope that these > features are pretty much complete for 1.8. > > 2) Just add release notes to 1.8 for the state as at the time of branching, > with everything else documented as a change from 1.8 > > 3) Don't "release" the new features at all in 1.8 (don't mention in release > notes). > > Any preferences? I like 1), but this will depend on the plan for releasing. I'd prefer option 2. Option 1 pushes out the release date as there's more stuff to review, and there will almost certainly be more breaking changes in 1.9. I think we just mention that this work is all still very much a work in progress, so use it if you like but be aware that it's not close to stable yet and you should wait for a few more releases before things become more stable. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle eXchange 2013, Oct 28th in London, UK: http://skillsmatter.com/event/java-jee/gradle-exchange-2013
