+1 for 0.7.1. Sounds more appropriate in this case. -- Andrei
On Tue, Jan 10, 2012 at 3:27 AM, Tom White <[email protected]> wrote: > +1 I think this is a good plan. What you describe is basically a > bugfix release, so it might be called 0.7.1 if it doesn't break APIs > or compatibility. > > Cheers, > Tom > > On Mon, Jan 9, 2012 at 2:48 AM, Andrei Savu <[email protected]> wrote: > > Hi Team, > > > > I was just taking a look over the roadmap for Whirr 0.8.0. I think the > top > > priority should addressing the lack of deterministic behaviour on cluster > > deployment - service start. A cluster should either start as expected or > > fail all the time. > > > > Some of the relevant issues are: > > > > * https://issues.apache.org/jira/browse/WHIRR-221 > > * https://issues.apache.org/jira/browse/WHIRR-266 > > * https://issues.apache.org/jira/browse/WHIRR-295 > > * https://issues.apache.org/jira/browse/WHIRR-294 > > * https://issues.apache.org/jira/browse/WHIRR-468 > > > > One possible workaround the we should be able to implement pretty soon is > > to give Whirr the ability to restart a specific role. > > > > I am also thinking that as soon as we close the listed issues we can cut > a > > release. > > > > What do you think? > > > > -- Andrei Savu / andreisavu.ro >
