On Friday we released the Takari Lifecycle 1.10.1 in response to an issue reported by Paris Apostolopoulos. Paris is very supportive of our efforts so we tried to get a release out for him and his team. From the time of reporting the issue to landing the new release in Maven Central was approximately 9 hours.

All of the Takari Lifecycle’s components are housed at Github so it was possible to make the set of cascading releases required and get the result to Maven Central relatively quickly. It’s awesome that you can have a conversation with a user on Twitter, get their assessment, figure out the issue, resolve the issue and push out a release as soon as possible. We think our users like this, and we certainly like being able to turn around fixes in a timely manner.

The conversation went like this:

@takari_io Hi, where do we submit a bug? for the 1.10 release, it seems there is a problem with the project compiles on Windows OS

— Paris Apostolopoulos (@javapapo) January 16, 2015

@javapapo @takari_io found the issue, will try to get this sorted asap

— Jason van Zyl (@jvanzyl) January 16, 2015

@jvanzyl @takari_io great many thanks for your time! We are committed takari users :D #maven #takari

— Paris Apostolopoulos (@javapapo) January 16, 2015

@javapapo we’ll get faster but from time of report to release in Maven Central was 9h — although we didn’t wake up until 5h ago :-)

— Jason van Zyl (@jvanzyl) January 16, 2015

We look forward to pushing out more releases of the Takari Lifecycle as fast as we possibly can! We have also noticed that users have been raising issues for the lifecycle chapter and we plan to make it easier this week for users to make pull requests directly to help us improve the content!

Comments