Mikhail Loenko wrote:
Actually there are important things that are to be tracked in JIRA.
For example, questions of being non-compatible with either RI or spec.
I personally don't care too much about which mailing list the JIRA
issues are sent to, because Thunderbird can handle them easily and well.
But I DO prefer to discuss on the mailing list, and JIRA can be used to
only reflect the stage or result of the discussion(that's my
understanding of status tracking, instead of discussion tracking :-) ),
another reason I prefer writing email than commenting on JIRA is email
is easier to be used as discussion - it can be read/replied/commented
off line, the previous mail can be inline, it can use html format, etc.
etc. ;-) .
A sample is the JIRA issue 184 about TimeZone serialization
compatibility, which itself is a concrete case, and I reply this JIRA to
dev mailing list to discuss more common compatibility issue, and when we
have some agreement on what to do, I will update the JIRA issue to
reflect that. I'm fine in this way.
And as far as the mail traffic on the dev-list is doubling every month [1]
it would be great to make it possible to separate those JIRA issues
that describe minor bugs/fixes from these ones that have conceptual value.
I agree with you that many JIRA issues are not as significant as some
others, especially as reference for similar case later, I guess there
are already some marker for this purpose, priority/type/component, etc.
Is it possible?
Thanks,
Mikhail.
[1] http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/
2006/3/7, S. Meslin-Weber <[EMAIL PROTECTED]>:
On Tue, Mar 07, 2006 at 09:19:54AM -0800, Craig Blake wrote:
Sweet, many thanks.
+1, I wasn't being flooded but it's nice to be able to separate these
flows without client-side filters.
Steph
--
================================================================
Stephane Meslin-Weber Email: [EMAIL PROTECTED]
Senior Software Engineer Web: http://odonata.tangency.co.uk
================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFEDcGV5QGfd9PDUN0RAhcUAJ9FFfB5zsxEiDxo0r/UkRCHobAU8ACfZGy2
9gq36aAlp5OfoHW/hyoyU4s=
=jI+O
-----END PGP SIGNATURE-----
--
Paulex Yang
China Software Development Lab
IBM
