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]
