Our plan for Gradle 1.0

(Adam Murdoch) #1

We are working intensely towards a Gradle 1.0 release. Here’s our plan for making this a reality:


Due for release in the next few days, 1.0-milestone-8 wraps up the bulk of our work on the dependency cache and daemon. While there is always more work we can do in these areas, we feel they are now more than good enough for a 1.0 release. We will certainly continue to work in these areas following the Gradle 1.0 release.


Approximately 4 weeks later, we will release 1.0-milestone-9. This release will contain the last few features that we want to finish up for the 1.0 release. At this stage, we’ll be feature complete for a 1.0 release.

We’ve had to make some hard decisions about which features are in the release, and which features have to wait. However, we feel confident that 1.0 is not the end of the story for build systems, and we will continue to innovate and evolve Gradle. So, if your favourite feature does not make it into Gradle 1.0, rest assured that we’ll be working hard to get it implemented in later releases.


Approximately 4 weeks later, we will release 1.0-rc-1. This release will contain the final bug fixes we want to make for 1.0. Based on the issues that are found with this release candidate, we will either release it as Gradle 1.0, or do another release candidate.

##After 1.0

Following Gradle 1.0, we plan to switch to a more traditional versioning scheme. We will continue with frequent releases every 4-6 weeks. So, you can expect to see either a Gradle 1.0.1 or 1.1 release 4 weeks after Gradle 1.0 is out, with the corresponding release candidate a week or two before this.

We are still planning exactly what we want to focus on post 1.0. Have a look at the roadmap for some details of the things we are thinking about.

(Bret G) #2

Is gradle 1.0 going to align with groovy 1.0? Will there be any performance gains with Groovy 1.0?

Gradle rocks !!!

(Peter Niederwieser) #3

Gradle 1.0 will be based on Groovy 1.8.x. I wouldn’t expect major performance gains from Groovy 2.0 because Groovy execution speed is typically not the bottleneck in a build.

(gradle-shorn) #4

You should consider updating the roadmap on the gradle.org site with a summary of this.

At a quick glance, it’s not clear that all the planned features aren’t for 1.0 - it gives the impression that Gradle 1.0 is still under heavy development and isn’t close. The link to the Issue Tracker makes things clearer, especially the “versions: due” part - but the big features section is what people read first.

(Luke Daley) #5

Thanks Shorn, we’ve created a todo for this.