The current components in jira are (with current # of categoried issues):
AOL Notifier 1
Core system 80
Database16
Documentation 12
IRC Notifier3
Jabber Notifier 3
Mail Notifier 14
MSN Notifier2
Notification5
Project Grouping1
SCM 18
Web
Breaking apart the notifiers are a good idea.
However, due to natural language sort, they are not grouped very
efficiently.
How about Notifier ___ instead?
So, expanding your ideas to a the eventual list, we wind up with ...
Core system 80
Database 16
Documentation 12
Integration M2
well thats a little more verbose then I was looking for, I was
thinking we could shove all the tool integration stuff together, and
all the notifiers together. I was envisioning
Core system 80
Database 16
Documentation 12
Tool Integration
Notification 5
SCM 18
Web UI 89
I think breaking out the tools and notifiers is a good idea. They are
actually the *easiest* ones for people to hit because they know which
specific one they are using.
How about breaking up core system into scheduling, etc? Also, is
there anything in those 61 no components that should be
well, when you look at it like that...
ok, I'll do that this weekend and try and get a home for those poor 61
lonely issues :)
jesse
On 11/10/06, Brett Porter [EMAIL PROTECTED] wrote:
I think breaking out the tools and notifiers is a good idea. They are
actually the *easiest* ones for people
Brett Porter wrote:
I noticed that artifacts and repositories is now accompanied by
artifacts, dependencies and deployment components in MNG.
I have to look back at what Natalie suggested but I believe it's
supposed to be
- artifacts
- repositories
- dependencies
- deployment
jvz.
I noticed that artifacts and repositories is now accompanied by
artifacts, dependencies and deployment components in MNG.
Was the original meant to be removed? What does artifacts mean if not
dependencies and deployment?
- Brett
I've had a stab at this - any feedback on extra components?
- Brett
Brett Porter wrote:
Hi,
I was wondering what folks though of changing maven-artifact,
maven-core, etc in JIRA to be user friendly components like:
* error reporting
* artifact deployment
* artifact resolution
etc.
These
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 from me for changing the components. Comments inline.
Jason van Zyl wrote:
| On Mon, 2005-11-07 at 10:20 +1100, Brett Porter wrote:
|
|Hi,
|
|I was wondering what folks though of changing maven-artifact,
|maven-core, etc in JIRA to be user
Sounds good to me and, as you said, users won't probably know which
component(s) is(are) affected anyway.
Cheers,
Stéphane
On 11/7/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
I was wondering what folks though of changing maven-artifact,
maven-core, etc in JIRA to be user friendly
On Mon, 2005-11-07 at 10:20 +1100, Brett Porter wrote:
Hi,
I was wondering what folks though of changing maven-artifact,
maven-core, etc in JIRA to be user friendly components like:
* error reporting
* artifact deployment
* artifact resolution
etc.
+1
Anything the user can identify
But the user
being able to file correctly in the first place is probably more
important.
I agree. I'm just wondering then why I never got an answer to my mail on
this: http://www.mail-archive.com/dev%40maven.apache.org/msg42387.html
-Lukas
Hi,
I was wondering what folks though of changing maven-artifact,
maven-core, etc in JIRA to be user friendly components like:
* error reporting
* artifact deployment
* artifact resolution
etc.
These often cover more than one physical component anyway and they are
more likely to be
13 matches
Mail list logo
