On Aug 22, 2013, at 8:12 AM, Andrew Phillips wrote: >> So this brings up an important question. We're about 6 weeks from the >> target date for 1.7.0 - can we actually get the blobstore stuff de-asynced >> by then? Or are we going to need to push the de-async completion back 'til >> 1.7.1/2/3/whatever? How high a priority should this be? > > To me, this has high priority because it's about getting the "new" provider > programming model in place, and with the new potential development community > at Apache I'd like to get this done as soon as possible, ideally in the first > major Apache release. > > If not all of the providers make it, that would be OK, I guess, as long as we > have sufficient "good" examples to point people towards. > > In order to help balance this out: what do we feel are the other Really > Important changes/features we're pushing out with 1.7.0, which we would > rather not delay?
I'm going to have a look at this this afternoon and try to figure out the scope of the work to de-async all of the OpenStack/Rackspace stuff. My initial suspicion is that it's going to be pretty thorny due to async stuff being used in BlobStore. We'll see. Everett
