Shorten Espresso release cycle

[GoogleCodeExporter]

Title says it all. There hasn't been a release of Espresso in 6 months. The 
community and the project could strongly benefit from a faster release cycle.

Original issue reported on code.google.com by benoitd...@gmail.com on 23 Aug 2014 at 12:21

[GoogleCodeExporter]

Yep, a more open project governance would help as well. I think many Android 
community members would happily supply patches / pull requests for improvements 
or bugfixes if these would be easier possible and - of course - actually 
handled.

Efforts like Jake Wharton's double espresso 
(https://github.com/JakeWharton/double-espresso) are good, but also show the 
surrend of said community when it comes to moving foward with this project.

Original comment by m...@thomaskeller.biz on 9 Sep 2014 at 1:00

[GoogleCodeExporter]

s/surrend/surrender/

Original comment by m...@thomaskeller.biz on 9 Sep 2014 at 1:01

[GoogleCodeExporter]

We're working on moving the project into AOSP. It's taking longer than I would 
want, but once it's finished, the plan is to move to much shorter release 
cycles (e.g. monthly). I love the idea of getting external contributions too.

Original comment by vale...@google.com on 23 Oct 2014 at 9:45

• Changed state: Accepted

[GoogleCodeExporter]

Nice. Any vague estimate? Even an incorrect one :)

Original comment by benoitd...@gmail.com on 23 Oct 2014 at 9:51

[GoogleCodeExporter]

Original comment by vale...@google.com on 16 Mar 2015 at 7:52

• Changed state: Done