I also want to move forward with the release, but I'd like to make sure we fix our broken windows in it. I agree with you Andrew G. that those tasks can be deferred, but I really think it is important to address the live test failures in this one.
There are failures in AWS compute (I'll volunteer to take a look at them), in the blobstore providers you mentioned, and there are also many failures in rackspace compute, that I've been reporting for several releases. Those failures should be addressed too in this release. If we want to say we support all major providers in the next release, we should fix the ones we already have in this one so we can focus on what we're missing for the next release. On 22 January 2015 at 20:02, Andrew Gaul <g...@apache.org> wrote: > On Thu, Jan 22, 2015 at 10:34:54AM +0000, Andrea Turli wrote: >> quick update on the must-have list: >> >> * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2]) > > I will take look at the aws-s3 live test failures this weekend. We also > have reports for failures against google-cloud-storage[JCLOUDS-805] and > rackspace-cloudfiles-us[JCLOUDS-800]. Bhathiya is looking into the > former; can someone from Rackspace investigate the latter? > >> * Remove the old Swift provider. > > We should not remove this api or its providers in 1.9.0 since its > replacement does not have feature parity, specifically multi-part upload > support[JCLOUDS-760]. However, if we could add providers for hpcloud > and softlayer this would allow many users to migrate. > >> * Support AWS signature version 4. (JCLOUDS-480 [3]) >> * Promote the OAuth API. It is now used only by GCE but if I'm not >> wrong it will be used by the DigitalOcean v2 api too. >> * Promote Google Compute Engine. >> - Fix all failing live tests (there are not many). >> - Remove its SecurityGroupExtension, as the current implementation >> and how firewalls work in GCE is not aligned with how the SGE works. >> * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5]) >> * Study the uses of the Apache HttpClient driver and consider >> migrating to the OkHttp one. The output of this task should be a plan >> to upgrade or remove the Apache HC driver. > > None of these seem like release blockers; can we defer them to 2.0.0? > >> * Support Docker 1.3.2 (Complete the corresponding PR [4]) -> closed >> >> For what I can see only Docker support has been closed. >> >> Do we have any update on the others? I'd really like to move faster to >> 1.9.0-rc release at least, so I'll be happy to help with any of them. > > I would also like to move forward with a release; master has almost six > months worth of features since the last major release and three months > worth of bug fixes since the last minor release. Can we identify any > blocking issues with fixVersion = 1.9.0 in JIRA: > > https://issues.apache.org/jira/browse/JCLOUDS-791?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.9.0 > > I will add a few other potential blockers. > > -- > Andrew Gaul > http://gaul.org/
