cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <>
Subject Re: [ASFCS42] Proposed schedule for our next release
Date Fri, 19 Apr 2013 15:53:20 GMT
On Fri, Apr 19, 2013 at 08:40:48AM -0700, Min Chen wrote:
> I like this idea too, this will be a much better channel for community to
> understand features to be planned. +1 to this.
> -min
> On 4/19/13 7:02 AM, "Prasanna Santhanam" <> wrote:
> >On Fri, Apr 19, 2013 at 10:16:35AM +0000, Murali Reddy wrote:
> >> 
> >> Pardon my ignorance of project management, but it appears to me we are
> >> talking of managing a release after half way through the cycle. May be
> >> this is orthogonal discussion, but how about taking approach of
> >>planning a
> >> release early in the cycle (at least for future releases)? Having a time
> >> window between each release where we actually plan for the next release.
> >> Discussions include - direction of the project, what big features are to
> >> be included, rough estimate of the effort, risks and timelines would
> >>help
> >> in planning releases better? Perhaps we should use Collab conferences
> >>for
> >> this purpose, where we can plan for the next release (apart from show
> >> casing the features of previous release). Since Collab is also scheduled
> >> to happen on a half-yearly timeline it makes this easier to execute
> >> release management starting from there.
> >
> >I actually like the idea of 'collab conference' to do release
> >planning! So +1 to that.
> >
> >-- 
> >Prasanna.,

I get the desire to do planning via an in-person meeting, but it's not
going to fly.  Here's the reason:  it's exclusionary.

We are an Apache project, and that means that the list is the place for
planning and decisions.

Now, that doesn't mean that we can't all have talk proposals to discuss
a feature we'd like to see at an event.  On the contrary, that's a great
talk topic.

I'll circle back to Murali's initial email to discuss some of the finer 
points of his post shortly.

View raw message