On 24-Mar-08, at 4:42 PM, Brian E. Fox wrote:
Right now there are approximately 4 times more issues in MNG under
documentation categories than there is in MNGSITE, so I think my hunch
about the users is right. If you want a report, just exclude
documentation...
So where they put it and where it should go for us is probably
different. I don't personally like looking at documentation issues
while I'm trying to look at runtime issues. That's just my preference.
But whatever I don't care as long as it's easy and _obvious_. It
took me
over a minute to find the right project (and I knew that it was
separate). We should do something useful with the old 1.x stuff cause
it's just in the way IMO. And the name of the project should be set so
that it comes up right next to "Maven 2" because right now it's buried
in a bunch of other random stuff on the default dashboard.
-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 7:35 PM
To: Maven Developers List
Subject: Re: Where to create JIRA issues for Maven documentation?
Yah, I actually agree with Dennis. I prefer them separate so I can
track runtime problems with Maven versus what we say about the
runtime.
On 24-Mar-08, at 4:25 PM, Dennis Lundberg wrote:
I disagree. For ourselves, as well as our users, having a separate
issue tracker for the site is a good thing. MNG is currently a
*large* heap of issues and different (JIRA) component, and I believe
it's difficult for a user to grasp. MNG is in my world about Maven -
the application, and that is not the same as maven.apache.org.
Brian E. Fox wrote:
I think it's easier for the users to find if it's a component of MNG
rather than separate. So I would suggest we move MNGSITE over to
MNG.
-----Original Message-----
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent:
Monday, March 24, 2008 11:39 AM
To: Maven Developers List
Subject: Where to create JIRA issues for Maven documentation?
Hi,
It seems there are currently two places in JIRA to fill in issues
regarding documentation:
- the components "Documentation: *" in project MNG and
- the project MNGSITE
Is this situation by design, i.e. are the projects/components
intended
for different purposes/audiences, or could we move the whole doc-
stuff from
MNG over to MNGSITE in order to have it in a central location?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
