Added information about project history and plans
@@ -22,6 +22,33 @@ If the vision of the project connects with you help us!!! Get in touch on the [m
- 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.
+## History
+
+- 2014, August - we set up automated [continuous delivery for Mockito](http://blog.mockito.org/2014/08/ready-for-continuous-deployment.html) project, every merged pull requested produced release notes and new version in Maven Central.
+We [still do it today](https://github.com/mockito/mockito/wiki/Continuous-Delivery-Overview) in Mockito!
+- 2016, November - we pushed out the release automation toolkit to a separate project in GitHub, called "mockito-release-tools".
+We really needed to do that!
+As much as useful the toolkit was to drive Mockito releases, we needed to make it reusable, well documented, and packaged as a separate binary.
+- 2017, February - [Marcin Stachniuk](https://github.com/mstachniuk) joins the team, implements automatic fetching of contributors from GitHub and starts working on automatic [e2e testing](https://github.com/mockito/mockito-release-tools/issues/85) of library clients.
+- 2017, March - [Wojtek Wilk](https://github.com/wwilk) joins the team, implements release avoidance when binaries aren't changed in comparison to previous release, starts driving [API compatibility](https://github.com/mockito/mockito-release-tools/issues/105) validation and Shipkit dogfooding.
+- 2017, April - we found a neat name for our project: "Shipit", a toolkit for shipping it! We registered the domain: http://shipkit.org
+- 2017, May - there are 5 contributors in total, we expanded the vision of the project, and currently working on killer features like: automated e2e testing with library consumers + automated pushes of version upgrades [#85](https://github.com/mockito/mockito-release-tools/issues/85), [A/B testing](https://github.com/mockito/mockito-release-tools/issues/113) of build results when upgrading dependencies.
+
+## Plans
+
+- 2017, June - we plan to release [1.0 of Shipkit](https://github.com/mockito/mockito-release-tools/issues/116) library during [Gradle Summit Conference](https://summit.gradle.com) 22-23th of June 2017, Palo Alto, CA. Core features offered by 1.0:
+ - version management
+ - automatic publication of binaries to well known public repositories
+ - release notes generation based on Git log and the issue tracker links
+ - avoiding releases when binaries are the same
+ - pulling information about contributors and including it in release notes and pom.xml files
+ - and all that in a sweet little package, fully integrated, neatly automated, easy to roll out
+- 2017, July - we will be present at [Confitura '17 conference](https://2017.confitura.pl) in Warsaw, PL, on 1st of July. We submitted a paper, if it gets accepted, Shipkit will be revealed in all its might!
+
+## Future
+
+The roadmap is comming soon!
+
### Testing
#### Release notes
