Comments inline below.
On Jul 27, 2011, at 4:30 AM, Mark McLoughlin wrote:
On Tue, 2011-07-26 at 09:54 -0500, Steve Loranz wrote:
> This is all stuff that should be in the feature description and update
> log *in Redmine*. We're already identifying target releases for
> features and tasks there, we're already tracking progress there, we
> can already see the last time it was updated there, who owns it, etc.
> I do think it is good to adapt some of this template to features and
> tasks in Redmine to urge better definition and updates, but I really
> want to keep one definitive place for features and tasks.
That sounds reasonable, so I took a look at how we could move the audrey
example into redmine but I got a bit stuck:
- are you suggesting that we'd file an issue on the Feature tracker
and then file child issues for each remaining tasks on the list?
Yes. I believe that this is done already to a certain extent. In Image Factory we have
been nesting like this for awhile.
- I'm not too keen on putting all this stuff in an issue
since it wouldn't be editable - a lot of it is high-level
documentation that should be updated as things change during
development. Perhaps the issue should just link to a wiki page?
I think that is reasonable.
- this template I put together is for much higher-level features
I'd expect to see as Redmine Features - e.g. the audrey feature I
wrote up should map to quite a few Redmine features
From the standpoint of using Redmine to plan releases and convey a roadmap to the
community, I think there is still value in having these high level features listed in
Redmine and showing the sub-features and tasks as children of it. The only rub may be
Redmine if it fails to deal with many levels of relationships. It might handle it fine,
I'm not sure yet.
- Audrey seems to be using Versions as a way of grouping related
issues. I don't think you're suggesting creating a Version to
represent a feature?
No. I mean versions in the release/milestone sense. As in, "We plan to release
something on <date> and we're calling it <version> and we expect to have
<list of features, tasks, bugs> in it."