Welcome to the October 2019 newsletter.
This issue covers the Gradle 6.0 RC1 release, the Gradle Enterprise 2019.3.3 release, early access to the Developer Productivity Engineering book, and the Productivity at scale: How [LinkedIn] improved build time with Gradle build cache blog post.
Make sure you are ready for the upcoming switch to HTTPs for Gradle Services. This Decommissioning HTTP for Gradle Services blog post explains if you may be affected and how to prepare.
If you have a talk, blog post, or plugin release you’d like us to share in the next issue, use #gradle
on Twitter or send us an email with the details to newsletter@gradle.com.
🎉🎉 The first release candidate of Gradle 6.0 is out! 🎉🎉
This release candidate includes many exciting new features and documentation updates including:
Gradle 6 is a breakthrough release in terms of dependency management. It is the culmination of several years of innovative improvements including Gradle Module Metadata and sharing dependency versions between projects via platforms.
Please try the release candidate and send us your feedback.
Gradle Enterprise 2019.3.3 is out fixing several issues raised against Gradle Enterprise 2019.3.2.
The highlights include:
We’ve released an early access version of our upcoming Developer Productivity Engineering book. This book is based on our collective experience learning how the world’s top development teams create a productive and joyful developer experience. Register today to get the pdf and email updates when new chapters and other related content are released.
Do you have a knack for technical writing and an interest in improving the Gradle build tool user experience? Then you might be a good fit for our open Developer Advocate position.
The ideal candidate will have excellent English writing skills (links to samples and writing portfolios welcome), experience using Gradle and/or Maven, and a passion for helping Gradle users. Spend some time writing a cover letter and then submit an application.
The Gradle Inc. engineering team continues to grow. We’re currently looking for:
The details of these and other open positions are available at gradle.com/careers.
If you have some news you’d like us to share in the next issue, use #gradle
on Twitter or send us an email with the details to newsletter@gradle.com.
Until next time!
—The Gradle Team
Gradle Inc. | 2261 Market Street #4081 | San Francisco, CA 94114
Privacy Policy | Unsubscribe