Hi,
FYI about planning, Francois's team developped a useful Jira plugin
[1]. It provides a planning dashboard.
Here is a sample project to see it live:
http://www.greenpeppersoftware.com/jira/browse/BANK
It is free for open source projects.
If you think it could be great for Maven and
Zyl [EMAIL PROTECTED]
Date: Wed, 1 Aug 2007 23:22:12
To:Maven Developers List dev@maven.apache.org
Subject: Re: how we handle JIRA versions
All looks good, my only comments are I think the notions in Scrum
like Sprints for a release are good like the idea of fixing the set
of issues
On 02/08/2007, at 2:02 PM, Brian E. Fox wrote:
It'd be nice to enforce it now, but I'm not prepared for that kind of
pain :) If someone else who's done more jira workflowy things wants
to try their hand, please do. Otherwise, I figure if we at least have
a stated pattern in agreement, if we
I hesitate to comment, as I'm not a team member here, but the
important thing in Scrum is the timebox, as well as the features/
issues. But if you run up against the timebox, you drop lower
priority features into the next sprint. This ensures regular
releasing, which ensures feedback,
this for a while... Should be easy
enough to impl... But does it already exist?
--jason
-Original Message-
From: Jason van Zyl [EMAIL PROTECTED]
Date: Wed, 1 Aug 2007 23:22:12
To:Maven Developers List dev@maven.apache.org
Subject: Re: how we handle JIRA versions
All looks good, my
Brett Porter wrote:
On 02/08/2007, at 5:31 AM, Dennis Lundberg wrote:
Excellent stuff Brett. Let me know if I can help.
Most of this is equally important for plugins and other maven sub
projects. We should try to make an additional, more general,
description of versions that is not tied to
@maven.apache.org
Subject: Re: how we handle JIRA versions
All looks good, my only comments are I think the notions in Scrum
like Sprints for a release are good like the idea of fixing the set
of issues and sticking with it for the Sprint. Sensible patterns and
there's already literature on that. So
enough to
impl... But does it already exist?
--jason
-Original Message-
From: Jason van Zyl [EMAIL PROTECTED]
Date: Wed, 1 Aug 2007 23:22:12
To:Maven Developers List dev@maven.apache.org
Subject: Re: how we handle JIRA versions
All looks good, my only comments are I think the notions
On 02/08/2007, at 8:12 PM, Dennis Lundberg wrote:
What is your definition of site and documentation. I'm not sure I
see how you mean. For me site is project related and documentation
is product related.
Yep, that's a good definition. I'm thinking here it's the difference
between
Hi,
A while back I promised to write up what we are doing with jira
versions now, and finally got around to it. In the process, I came up
with a couple of tweaks we could make (see actions). Here it is in
point form - does everyone agree this is the process we are following
now? Missing
Excellent stuff Brett. Let me know if I can help.
Most of this is equally important for plugins and other maven sub
projects. We should try to make an additional, more general, description
of versions that is not tied to MNG.
I have a couple of questions, see inline...
Brett Porter wrote:
On 02/08/2007, at 5:31 AM, Dennis Lundberg wrote:
Excellent stuff Brett. Let me know if I can help.
Most of this is equally important for plugins and other maven sub
projects. We should try to make an additional, more general,
description of versions that is not tied to MNG.
Agreed, I
All looks good, my only comments are I think the notions in Scrum
like Sprints for a release are good like the idea of fixing the set
of issues and sticking with it for the Sprint. Sensible patterns and
there's already literature on that. So in any parts you're talking
about planning I
On 02/08/2007, at 1:52 PM, Jason van Zyl wrote:
I'd encourage us sharing a good Mylyn set up and putting it on the
web site to encourage this consistency, but I think it's
unreasonable to mandate it.
Why? It's free and it's the best way to keep some level visibility.
For people
On 02/08/2007, at 1:22 PM, Jason van Zyl wrote:
All looks good, my only comments are I think the notions in Scrum
like Sprints for a release are good like the idea of fixing the set
of issues and sticking with it for the Sprint. Sensible patterns
and there's already literature on that. So
On 1 Aug 07, at 11:37 PM 1 Aug 07, Brett Porter wrote:
On 02/08/2007, at 1:22 PM, Jason van Zyl wrote:
All looks good, my only comments are I think the notions in Scrum
like Sprints for a release are good like the idea of fixing the
set of issues and sticking with it for the Sprint.
It'd be nice to enforce it now, but I'm not prepared for that kind of
pain :) If someone else who's done more jira workflowy things wants
to try their hand, please do. Otherwise, I figure if we at least have
a stated pattern in agreement, if we see regular violations we should
either
17 matches
Mail list logo
