Re: [cowiki-dev] New feature implementations and bug fixes

We need to finalise our milestone goals and then make sure that all
features are assigned to the right milestones.  This would give us a
list of the features which are important goals for the next major
release.

Then for each feature there could be a document describing the goals
of the feature, pointing to any interesting issues in the tracker and
such.  This is something I can do.

A system like this would let regular users look inside what coWiki is
intending to do and to read about the features without leaving the
safety of cowiki.org and venturing into the dark depths of the issue
tracker or mailing list archives.  =)



On 6/22/05, PAUL HANCHETT <[email protected]> wrote:
>  'Morning Team!
>  
>  For the future I want to have a brief outline of how new features or fixes
> will appear to users.  The problem is that sometimes added features and
> (significant) bug fixes are working in ways that I had not thought to
> anticipate.  (You are a *very* creative bunch!)  I would rather negotiate a
> feature beforehand than tell you it needs to be changed later...  It would
> also give an opportunity for the team to review functionality and offer
> suggestions for improvements.
>  
>  This would provide our first (user) documentation of how a feature is
> intended to work.  It would be a great start for a documentation writer.
>  
>  My goal is not to keep anyone from doing the Right Thing or to distract you
> from your coding, but rather to agree where we are going with the changes we
> make.  
>  
>  The alternative might be to review all changes before they are committed to
> coWiki's main trunk.  That would be OK, but cumbersome, if that's what you
> wanted to do.
>  
>  Discussion?
>  
>  Paul
>