Simple and practical Continuous Delivery for Open Source and enterprise

[mockitoguy]

Imagine

Imagine the world where you call pull in a new version of some Open Source library and not worry if it breaks compatibility. Imagine that you can submit a pull request to some project, have it reviewed timely, and have the new version with your fix available to you in minutes after your PR is merged. Imagine that for any dependency you consider upgrading, you can view its neatly and consistently maintained release notes. Imagine that you can set up practical Continuous Delivery automation in your project in minutes, by using a well behaving and documented Gradle plugin. Imagine that you can focus on code and features while the release management, versioning, publishing, release notes generation is taken care for you automagically.

This is the goal of "mockito release tools project".

True North Star

The goal Mockito Release Tools project is to provide easy-to-setup Continuous Delivery tooling. We would like other teams to take advantage of rapid development, frictionless releases and semantic versioning just like we do it in Mockito. We plan to make our release tools generic and neatly documented. It will be a set of libraries and Gradle plugins that greatly simplify enabling Continuous Delivery for Java libraries.

We need help

We cannot achieve our goals without your help. Consider joining our efforts! Help is requested for:

• Implementing features - see the issue marked with "please contribute" label.
• Using the release tools in your project and giving us feedback.
• Spreading the word of what we're doing, letting us know about other project with similar goals. You can GitHub issue tracker for reaching out.

If the vision of the project connects with you help us!!!