On 18/02/2008, at 9:03 AM, Jeff Jensen wrote:
Possibly there are some to close (won't fix/won't do the
enhancement), but
what is the reasoning for a bulk close of all of them?
I think the reasoning is that they are all won't fix at this point -
but they should certainly be reviewed first.
If consolidating all to one JIRA is of some benefit, then why not
just bulk
move those not closed to the "new one" (after processing them per the
above)?
Yeah, that might make more sense thinking about it. You want to keep
the roadmap/release notes for the old plugins releases, right?
And consolidating to one - I'd like to see arguments on it. So far,
the 3
of you are easily for doing it, but I am not sure of the "real
benefit". I
have some thoughts on the pros, but some cons too! :-)
Easier management if it is to be used going forward, much cleaner
interface for people filing bugs at codehaus :)
- Brett
-----Original Message-----
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 17, 2008 3:39 PM
To: Maven Developers List
Subject: Re: JIRA for Maven 1.x?
I thought maintenance mode also meant that people can still submit
patches to existing issues and we'll consider them.
However, given the small expected impact I think it would be most
practical to just close all open issues (plugins and core) as won't
fix,
and install a consolidated jira where people can still report new or
re-open old issues if they want them fixed.
Cheers,
-Lukas
Brett Porter wrote:
what does maintenance mode mean?
IMO, it would be that new issues can be reported, and are either
fixed
or closed as "won't fix" because they are new work or non-critical.
In
which case I would say:
- consolidate the projects (I'm not sure what this means in
practicality - I think you need to keep a project open but remove
*all*
of it's permissions for the old issue links to redirect to their new
home)
- close out any open issues that aren't going to be fixed
- leave permissions as is for the consolidated project.
Cheers,
Brett
On 18/02/2008, at 8:12 AM, Lukas Theussl wrote:
I wanted to propose that too, but what to do with the issues that
are
open? As long as m1 is in maintenance mode, I think we should keep
reported issues visible. We could remove the 'create new issue'
option from all projects though and update the description to point
to the new jira to use.
-Lukas
Brian E. Fox wrote:
What if all the maven 1.x jira projects where collapsed into one?
-----Original Message-----
From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Sunday,
February 17, 2008 3:34 PM
To: Maven Developers List
Subject: Re: JIRA for Maven 1.x?
If I'm not mistaken we didn't get a single critical bug report
after
1.1
was released. But that's not surprising, after all, it's a perfect
product... :)
I am not sure about closing the JIRAs, after all, maintenance mode
means
that we still do accept bug reports, right? If anyone would
submit a
patch or report something critical, I would still be willing to
apply/fix it and do a release. But given the late activity, this is
not likely to happen.
I'd agree to close the sandbox plugins, I wanted to do that myself
already a long time ago.
-Lukas
Brett Porter wrote:
Hi,
Some questions for the guys that wrapped up Maven 1.1 :)
Since Maven 1.x is in maintenance mode, should most of the
current
JIRAs that reflect things that won't be fixed be closed out?
At what point will we stop accepting new bugs?
And how does this affect the plugins - are they in the same state?
Thanks!
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
