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.
On Jul 26, 2011, at 6:05 AM, Mark McLoughlin wrote:
Now that we're getting the plans for the next release in good shape, I
think it'd be a good idea for think hard about which of the features
we're adding is going to be the most interesting to users.
I think each of those features should have an owner who understands the
big picture and how all the pieces of the feature fits together. The
feature owner should understand what makes the feature interesting and
how to quickly show off the best bits. The owner should know what
remains to be implemented and which the tasks absolutely must be
finished before releasing.
I'm basically suggesting something similar to the Fedora feature
process, but without any bureaucracy. All we want to get out of this is
a sharper focus on the things that matter to users.
So, here's a template for what I have in mind:
And here's an attempt to describe Audrey in this format:
aeolus-devel mailing list