Hi Andrei, My major concern will be full HBase support, for CDH, 0.90.x and onwards, Hadoop Append and so on.
I like to hear from others though about your thoughts. I am happy to discuss them but do not have a strong opinion at the moment. Adding more services is a great idea, this will show the versatility and raise interest. As for the cloud providers, what is left? Which one are not not supported yet but you think should? Which have missing features (if there are any missing ones)? How is using the Python scripts? I would add a deprecation warning in 0.5.0 and then remove it in the 0.6.0. - though they are outdated it does not really ask for a quick removal. Unless there is no one using it and then it could be dropped right away, no? I would love to volunteer as release manager but honestly am in the trenches writing the HBase book. So I would then do the one after that. I certainly +1 your suggestion and seeing the awesome job you have done this release I would love to see you handle another one :) Lars On Thu, Mar 31, 2011 at 12:22 PM, Andrei Savu <[email protected]> wrote: > Hi guys, > > How about doing some planning for 0.5.0? > > Some questions I'm thinking about: > - Should we focus on adding more services or on adding more cloud providers? > - Are there any JIRAs that we need to address as soon as possible? > - What's your short list of changes for 0.5.0? > - Should we have some sort of strategy for promoting the project so > that we can attract different communities to add services to Whirr? > - 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 >
