It's all going to wind up in JIRA anyway so why not just do it there to begin with?
That way we don't have to reconcile two things. My 2 cents. Everett P.S. I'm in a book sprint for the next two days so I'll be unavailable. See you next week! -----Original Message----- From: Ignasi Barrera [[email protected]] Received: Wednesday, 22 Jan 2014, 5:42PM To: {[email protected]} [[email protected]] Subject: Re: Roadmap for 1.8.0 and beyond? I'd like to have that so we can all be aligned, and users will have an idea of what will be implemented. This is my wish list: * Finish the site rebranding and improve the documentation. * Create a specialized TemplateBuilder that allows to set arbitrary CPU and RAM. This will allow us to properly model providers that don't use hardware profiles. * Complete the VolumeExtension for the ComputeService. * Give som love to the Clojure bindings; make sure they are up to date and usable. Shall we create a wiki page, discuss this here or use JIRA to define the backlog? On 22 January 2014 19:36, Andrew Phillips <[email protected]> wrote: > Picking up from discussions last year about our release cadence [1]...would > it make sense to try to put together a draft backlog for 1.8/2.0 and beyond, > to see what development capacity we're likely to have and hence what can > realistically be done? > > ap > > [1] http://apache.markmail.org/thread/fa6lpg7bbq32ayfl
