Hi Leo 2006/3/10, Leo Simons <[EMAIL PROTECTED]>: > Hi Mikhail! > > On Thu, Mar 09, 2006 at 10:34:46AM +0600, Mikhail Loenko wrote: > > Actually there are important things that are to be tracked in JIRA. > > Err...here's that rule again: > > Really Important Things MUST Go In SVN And/Or Onto The Public Mailing List
Well, that does not mean that they must not go into JIRA, right? Geir has created category "Non-bug differences from RI" [1] and those differences are to go there. <note> I'm not saying that discussions of the differences are to go there </note> Actually JIRA issues can be splitted this way: obvious stuff (like wrong method signature or wrong constant value in classlib) and non-obvious stuff (someone can disagree with the issue once it is created). Normally obvious stuff is interesting for the person opening the issue and a committer applying a patch. Non-obvious stuff is interesting for other people also. What I suggest is to separate those two kind of issues. For example, we can try to separate Trivial issues from other ones. Thanks, Mikhail [1] http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200602.mbox/[EMAIL PROTECTED] > > For example, with the accepting of external contributions, we receive > the files in jira, but the vote to accept them is on the mailing list, and the > forms and paperwork go on paper and in SVN, and the code ends up in SVN too. > > > For example, questions of being non-compatible with either RI or spec. > > Questions and their answers should also not go into jira. The ASF supports the > use of jira as an issue/bug tracker, but it is not supposed to be a > "communication hub". This isn't a "best practice", but a *hard rule* that's > there because of oversight / data integrity / openness / transparancy needs. > > > 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. > > > > Is it possible? > > Sure! the sky is the limit. If you take a stroll across the ASF jira, you'll > see how different projects have set this up differently. Its possible to have > different notification schemes for different components, different projects > (eg HARMONY, HARMONY-VM, HARMONY-CLASSLIB), different priority levels, custom > priority levels, and more (the documentation for jira at the atlassian website > is public I think and gives a good idea of the options). Its possible to have > a seperate mailing list, or even multiple ones. > > I think geir, me, dims all have admin privs for jira, I think tim might've > those too. The hard part is everyone agreeing on how things should be set up, > the actual administration work to change the config is just a few minutes. > > cheers, > > Leo >
