Sounds fine to me (there is a design component that can be used).
Let's leave responsibility of the original poster to follow an issue
through to conclusion. I still have the dev process flagged, for
example. I could just as easily file that to start with.
The main thing I want to avoid is using JIRA for design discussions.
That is always problematic when it happens. List posting works best,
possibly with summaries on the wiki.
Cheers,
Brett
Jason van Zyl wrote:
Hi,
I wanted to field ideas on how to track development/project
issues/discussions. Lately with the volume of mail I myself have found
it difficult to keep track of things we have been discussing. A couple
topics I remember are:
- standard j2ee layout
- our own development process
But sifting through mail can get difficult and there is generally no
easy indicator associated with documents as to whether something has
actually been resolved or not.
I was thinking that a simple solution would be to have a component in
the MNG JIRA projects for items like the two mentioned above. Then you
could see what discussions where started and still in progress and
historically you could see what major issues were resolved.
Vincent, Brett, Carlos, and myself are trying to gather content for a
book and I know that things I'm supposed to write about I can't write
about because there are some issues with our practices that need to be
resolved like:
- best practices for multi project setups
And there are general architectural issues like:
- how are we going to make additions to the POM and guarantee
backward/forward compatibility when we do (for example I want to add
site staging elements and categories for indexing projects).
I figure that a JIRA component would be the simplest and easiest thing
to do and it could reference wiki pages or mailing list discussions.
Any thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
