Fine. I can start working on these 2 issues.
On Sun, Oct 13, 2013 at 12:25 AM, Tomaz Muraus <[email protected]> wrote: > 1. This one has already been discussed and someone just needs to code it > at this point. Your are more than welcome to do so :) > > 2. First iteration of this task has already been merged in a trunk quite a > while back. > > Other future changes shouldn't be backward incompatible since it's just > adding sub classes. > > You are more than welcome to work on this one as well. If we tackle this > task for 1.0.0 we should do it completely. This means updating all the > drivers to use those new exceptions which is going to take decent amount of > work. > > > On Sat, Oct 12, 2013 at 5:17 PM, Jayy Vis <[email protected]> wrote: > >> Also, there are few important changes pending which may not be backward >> compatible. >> >> 1. Adding stopped state >> https://issues.apache.org/jira/browse/LIBCLOUD-296 >> >> 2. Raising ProviderError instead of Exception in >> libcloud.common.base.Response >> https://issues.apache.org/jira/browse/LIBCLOUD-331 >> >> I think we should get these changes into main stream for 1.0.0. >> >> I can work on these, if you guys vote up. >> >> Thanks >> Jayy >> >> >> On Sat, Oct 12, 2013 at 7:18 PM, Tomaz Muraus <[email protected]> wrote: >> >> > Yeah, launching the redesign at the same time we do the 1.0.0 release >> makes >> > a lot of sense :) >> > >> > >> > On Sat, Oct 12, 2013 at 3:40 PM, Sebastien Goasguen <[email protected] >> > >wrote: >> > >> > > >> > > >> > > >> > > On 12 Oct 2013, at 15:30, Tomaz Muraus <[email protected]> wrote: >> > > >> > > > Forgot to add this option - 0.14.0 will contain quite a lot of new >> > > features >> > > > and changes so another option is to skip 0.14.0 altogether and go >> > > directly >> > > > to 1.0.0. >> > > > >> > > > I plan to do a RC before next version in any case, but there is >> still a >> > > > chance that some bugs will slip through and make it to the final >> > 0.14.0 / >> > > > 1.0.0 release. >> > > > >> > > > If we do 0.14.0 release first, we have more time to fix those bugs >> for >> > > > 1.0.0. >> > > > >> > > >> > > I'd be +1 on 0.14.0 and then taking couple weeks for us to do a little >> > > cleanup, bug squashing and a few new func in some drivers. >> > > >> > > We could do 1.0.0 at the same time that we launch the new website ? >> > > >> > > >> > > > >> > > > On Sat, Oct 12, 2013 at 2:44 PM, Jerry Chen <[email protected]> >> wrote: >> > > > >> > > >> >> > > >> On Oct 12, 2013, at 6:29 AM, Tomaz Muraus <[email protected]> >> wrote: >> > > >> >> > > >>> As noted above, Libcloud has already been used in production for a >> > long >> > > >>> time and the base API has been relatively stable, so I propose we >> > > switch >> > > >> to >> > > >>> 1.0.0 after the next release (0.14.0). >> > > >>> >> > > >>> Some of you might say that it's confusing to switch directly from >> > > 0.14.0 >> > > >> to >> > > >>> 1.0.0 because 1.0.0 mostly likely won't contain any major changes. >> > > >> >> > > >> +1 to semantic versioning. >> > > >> >> > > >> Perhaps we can use this opportunity to also relaunch the libcloud >> > > website? >> > > >> I think it's about time we feature a direct download >> call-to-action, >> > as >> > > >> well as maybe the current contents of the "Getting Started" page on >> > the >> > > >> front page. Just a thought. >> > > >> >> > > >> Jerry >> > > >> >> > > >> >> > > >> > >> > >
