Discussion of future development of Shipkit.
- works well for projects like Mockito and few others
- release notes are beautiful ;-)
- adoption is small (too opinionated? / too complicated?).
- hard to resolve "challenging" issues that are not inline with Shipkit core design (concurent PR merging: #395, multiple build invocations before release: 858
- resolve "challenging" issues
- reduce complexity:
- componentize (few smaller plugins, strip unnecessary features, some progress in shipkit-auto-version)
- reuse smartly (for example: github-changelog-generator, jsemver)
- decouple, make it easy to use outside of Travis CI, Bintray (example #842)
- make Shipkit useful for projects like ambry, azkaban)