From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Are there plans to make the prioritization of bug fixes (and anticipated timeline) more explicit in the issue tracker? The Gradle feature set seems pretty mature at this point, so I’m usually much more interested in the fixing of bugs than I am in the introduction of new features.

I’m thinking of issues like <https://github.com/gradle/gradle/issues/1015>. It’s been open for 5+ years. At submission a Gradle employee remarked:
&gt; Thanks for the good bug report. I imagine we’ll tackle this in the not-too-distant future as we continue to improve the speed and correctness of incremental builds.
This is still open and it can be a pretty huge gotcha the first time you hit it, and then every subsequent time that you forget this doesn’t work properly.

polishing existing features is a big part of our focus

the problem with GitHub issues is that there are so many of them :slightly_smiling_face: (almost 2000)

is there a separate internal system for prioritizing/tracking bugs then?

we do have an internal system for tracking larger initiatives and the outcomes are now exposed via the public roadmap

we also take into account the publicly reported issues, for example to identify problematic areas and top-voted issues

and we have a dedicated team responsible for triaging all incoming issues

What is the timeframe in which a feature is in incubating mode? Is it fixed or dynamic, depending on the feature? :thinking_face:
I'm mainly interested in project accessors and in configuration cache!

we are working towards making configuration cache stable later this year but many teams us it in production already with great impact

I'm not sure about project accessors, <@UAB9WQKJ4> do you know?