On 30/08/2006, at 6:10 AM, Wendell Beckwith wrote:
For my team, I have been using, with minor adaptations, the eclipse
dev
process and in general I think it has the right amount of
"agility". We
post our plan early with our commited, proposed, deferred and
rejected items
for the next release and we revise it through out the release
process. We
use confluence for posting so that people interested in it can
subscribe
just to that page to cut down on unwanted emails. Therefore, when
we make
updated everyone who wants to be notified is notified and they can
either
comment on the issues we have attached to each plan item or start a
forum
discussion. I've create a template that maybe of use to you all if
you
wanted to go this way.
We use the JIRA roadmap. I'd be surprised if this is far different
from what you are doing, with the exception that:
- we are currently stalled. There is no trunk activity because our
focus is elsewhere (if anyone has time to pick things up and run with
them, great! No need to wait for the rest of us :)
- we only really start putting dates to things once there is some
momentum, and that's when the feature cull happens and it gets
constantly reviewed to try and get things happening regularly.
But I'm not adverse to having more visible documentation of what we
have to do and when we think we might be able to do it. It will help
getting people focused on things, and introduce a way in for
contributors.
> 2.) Produce nightly and weekly integration builds.
We already do. We could do it better. I've brought this topic up a
couple of times on the Continuum list.
I'm not on that list but I guess I will have to be to get a better
picture
of what's going on.
I expect this to become much more prevalent soon as Continuum is
getting the features we need to support it.
I'm happy to guide you into any area where you are interested to help
out. So, is it documentation that you want to help with? We have a
list of outstanding tasks which I can put in one place.
Or would you like to help pull together the roadmap for external
consumption?
I'm open to working with either or both. I do believe that
production of
the roadmap can help guide how to prioritize what documentation
will be
needed and when though.
Ok, how can we help get you started?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
