> I think that the Wiki page might be used for holding some transient info,
> but we can have a link from the page to the status file in the CVS. The
> Wiki isn't secure enough to hold the official planning documents. If it
> were, I'd prefer to use the Wiki to keep the status page. Perhaps when the
> Wiki built on top of Subversion is ready we'll change the mechanics.
The problem with status files is that they need to be religiously
maintained, otherwise the file is useless. I'd suggest sticking new
features into bugzilla for these reasons:
1. Requires devs to document the feature before writing it. Ideally, the
docs would be use cases/user stories.
2. Provides a nice place to document feature tests, even post automated
tests that can go into the test suite. It would be good to require a test
case or three for a given feature.
3. Keeps the tool count low.
4. Keeps status visibility high. Interested users will gravitate to
bugzilla to see what's going on; this way they can see the whole picture in
one place. Storing status in CVS is very close to evil because few will
actually find it. Besides, status is a snapshot, not a versioned resource.
It isn't going to be branched, merged, rolled back.
5. We can generate a unified bugs/feature status report from it. Helps
everyone know when the work is done or when the features are going in too
fast and the product is getting unstable.
Matt Bishop
[EMAIL PROTECTED]
"We are all here on earth to help others. What I can't figure out is what
the others are here for."
- W. H. Auden
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
