In terms of pacing, releasing in March or April feels right, more important than any feature. We should support Java 8 and include Guava 16, modernizing our APIs for the latter. We should consider taking dependencies on Java 7 features like larger than 2 GB payloads for HttpURLConnection, possibly dropping Java 6 support. I would like to create a compatibility matrix of which features different cloud providers offer and jclouds support for those, e.g., checksums, multi-part upload, user metadata. I would also like to improve support for S3 work-alikes, which often implement only a subset of the API. My attention will likely be diverted for the next month, but I can contribute to all of these in the coming months.
On Wed, Jan 22, 2014 at 07:36:38PM +0100, Andrew Phillips wrote: > Picking up from discussions last year about our release cadence [1]...would > it make sense to try to put together a draft backlog for 1.8/2.0 and beyond, > to see what development capacity we're likely to have and hence what can > realistically be done? > > ap > > [1] http://apache.markmail.org/thread/fa6lpg7bbq32ayfl -- Andrew Gaul http://gaul.org/
