That makes sense to me as well. Not a big deal to switch over - it was probably worth trying the other way first.

WILL

----- Original Message ----- From: "Nathan Bubna" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
Sent: Monday, September 26, 2005 3:32 PM
Subject: Re: new Tools JIRA project


+1 after my expedition through velocity's jira account last week, i
agree that the "Tool 1.2" thing is not ideal.  let's make it a
separate project.

On 9/26/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> Which is easiest for the developers?  I'm guessing that
> changing Component  to Tools and the release schedule to "Tools 1.2"
is probably
> pretty easy.

I was out the past 10 days on vacation, not reading -any- cisco.com
emails. And now I am digging through the 1200 in the queue. ;-)

+1 on a separate project for the reasons Will noted:
> different developers and different release schedules.

I have found that Jira works best when there is one versioned product
per project.

-1 on throwing versions into the component name (ala "Tools 1.2")
because this gives a confusing "roadmap" view with tools 1.2 and "1.5"
coming later. Tools is released separately from Velocity core... I say
we keep them separate.

Also -- for reporting a bug -- there will be a mixmash of the "Affects
version"...and it just won't make sense.

If users stick the issue/task into the wrong project, it's easy to move
it into the correct project. Also, components in core are different from
those in the Tools sub-project -- it would be a mixmash to combine them,
IMHO.

I'd be happy to create the new project.

-Timo

---------------------------------------------------------------------
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]

Reply via email to