Sounds good to me. We can leave this week to finish aliyun-ecs and do some release cleanup, then start the release next Monday.
On 30 July 2018 at 10:29, Andrea Turli <andrea.tu...@gmail.com> wrote: > Jia, > > Thanks for letting us know about Apache Pulsar usage of Apache jclouds: > it's an awesome news! > > Ignasi, all, > > I'd like to have aliyun-ecs into jclouds-labs before cutting 2.1.1 > Would it be possible to wait a couple of more days for you guys? > > Andrea > > > On Mon, Jul 30, 2018 at 5:32 PM Ignasi Barrera <n...@apache.org> wrote: > > > Hi Jia, > > > > We are holding the 2.2.0 release until we have moved to Java 8. There > are a > > couple outstanding issues there we need to address before releasing, so > it > > is unlikely to have a 2.2.0 release in the very short term. > > > > I see no reason to wait for 2.1.1 though, so if no one says otherwise, > I'll > > cut the 2.1.1 release this week. > > > > > > I. > > > > On 30 July 2018 at 01:26, Jia Zhai <zhai...@apache.org> wrote: > > > > > Hi dear jclouds developers, > > > > > > This is Jia, and I am working on Apache Pulsar. Thanks for your great > > work, > > > and recently we use jclouds in Pulsar. Would you please shed some light > > on > > > Jclouds release planning for 2.1.1 and 2.2.0? > > > > > > Currently we meet this issue: > > > https://stackoverflow.com/questions/49078140/jclouds- > > > multipart-upload-to-google-cloud-storage-failing-with-400-bad-request > > > , > > > since the fix is not included in a release, we have to use the snap of > > > latest jclouds code. > > > It would be great to know when the release with this fix will be > > available, > > > and then we could plan the next release of Pulsar. > > > > > > Thanks a lot. > > > -Jia > > > > > >
