On Thu, Mar 31, 2011 at 3:52 PM, Andrei Savu <[email protected]> wrote: > Hi guys, > > How about doing some planning for 0.5.0?
+1, way to go ;) > > Some questions I'm thinking about: > - Should we focus on adding more services or on adding more cloud providers? IMHO, completing service can take priority. But again, the best way is get the community feedback and decide. > - Are there any JIRAs that we need to address as soon as possible? > - What's your short list of changes for 0.5.0? 1. solidify documentation is one thing that I can think of. Agree that whirr is simple to use, but who start using it need helpful information to satisfy their needs like a person looking for Cassandra related stuff would like it specific to it, rather than having to move through complete doco. Probably, it would be as simple as adding more samples in doco. 2. FAQ's need to be strong, and simple way to build them is incrementally adding the resolution of issues discussed in ML's 3. Presentation page need some luv. BTW, your whirr presentation on slideshare must be added to this page :) > - Should we have some sort of strategy for promoting the project so > that we can attract different communities to add services to Whirr? blog/tweet, and probably plan a session in upcoming ApacheCon :) > - Is this the right moment to remove the Python contrib or we should > wait for one more release? > > In the near future I'm going to work on making Whirr more useful for > build artefacts testing (e.g. automatic local file uploads to blob > stores) and on Puppet integration. > > If we are aiming to release 0.5.0 by the end of June and no one else > wants / has time to be a release manager I could do this one more > time. For the next 3 months I'm going to work mostly on Whirr. > > Cheers, > > -- Andrei Savu / andreisavu.ro thanks ashish
