You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Will Glass-Husain <wg...@forio.com> on 2005/09/18 21:32:42 UTC
new Tools JIRA project
Hi,
What do you think about creating a separate JIRA project for Velocity-Tools? I think I have Karma to do this.
The reason is that I'd like to start categorizing all Velocity bugs for different releases. But Tools is on a different release schedule. I think we could move all open Tools bugs by hand (there doesn't seem to be a lot) and skip the import issues.
Nathan, Tim, others - comments?
Best,
WILL
Re: new Tools JIRA project
Posted by Will Glass-Husain <wg...@forio.com>.
I suspect reporters will frequently fail to set either option correctly :-)
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.
In any case, it's the job of the developers to assign to a release so this
has to be done regardless.
WILL
----- Original Message -----
From: "Nathan Bubna" <nb...@gmail.com>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Sent: Sunday, September 18, 2005 1:34 PM
Subject: Re: new Tools JIRA project
I'm ok with Henning's suggestion of differentiating Tools release
numbers and core release numbers by labeling them "Tools 1.2" and
"Core 1.4", and i'm also fine with just having separate projects. i'm
+1 for either plan. though i do wonder which is less confusing for
reporters...
On 9/18/05, Will Glass-Husain <wg...@forio.com> wrote:
> Essentially, different developers and different release schedules. The
> main
> Velocity project contains the core engine and has historically been
> released
> at infrequent intervals, while the Tools project has built up a nice
> framework around Velocity and has released more often.
>
> WILL
>
> ----- Original Message -----
> From: "sgtmcd" <sg...@sgtmcd.com>
> To: "Velocity Developers List" <ve...@jakarta.apache.org>
> Sent: Sunday, September 18, 2005 1:15 PM
> Subject: Re: new Tools JIRA project
>
>
> > Will Glass-Husain wrote:
> >
> >>Hi,
> >>
> >>What do you think about creating a separate JIRA project for
> >>Velocity-Tools? I think I have Karma to do this.
> >>
> >>The reason is that I'd like to start categorizing all Velocity bugs for
> >>different releases. But Tools is on a different release schedule. I
> >>think we could move all open Tools bugs by hand (there doesn't seem to
> >>be
> >>a lot) and skip the import issues.
> >>
> >>Nathan, Tim, others - comments?
> >>
> >>Best,
> >>WILL
> >>
> >>
> > I don't have a true opinion on this......but I do have a question. why
> > is
> > there a velocity-tools project? From a laymens point of view, it seems
> > that the projects should be one.
> >
> > regards,
> > Shawn
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: new Tools JIRA project
Posted by Nathan Bubna <nb...@gmail.com>.
I'm ok with Henning's suggestion of differentiating Tools release
numbers and core release numbers by labeling them "Tools 1.2" and
"Core 1.4", and i'm also fine with just having separate projects. i'm
+1 for either plan. though i do wonder which is less confusing for
reporters...
On 9/18/05, Will Glass-Husain <wg...@forio.com> wrote:
> Essentially, different developers and different release schedules. The main
> Velocity project contains the core engine and has historically been released
> at infrequent intervals, while the Tools project has built up a nice
> framework around Velocity and has released more often.
>
> WILL
>
> ----- Original Message -----
> From: "sgtmcd" <sg...@sgtmcd.com>
> To: "Velocity Developers List" <ve...@jakarta.apache.org>
> Sent: Sunday, September 18, 2005 1:15 PM
> Subject: Re: new Tools JIRA project
>
>
> > Will Glass-Husain wrote:
> >
> >>Hi,
> >>
> >>What do you think about creating a separate JIRA project for
> >>Velocity-Tools? I think I have Karma to do this.
> >>
> >>The reason is that I'd like to start categorizing all Velocity bugs for
> >>different releases. But Tools is on a different release schedule. I
> >>think we could move all open Tools bugs by hand (there doesn't seem to be
> >>a lot) and skip the import issues.
> >>
> >>Nathan, Tim, others - comments?
> >>
> >>Best,
> >>WILL
> >>
> >>
> > I don't have a true opinion on this......but I do have a question. why is
> > there a velocity-tools project? From a laymens point of view, it seems
> > that the projects should be one.
> >
> > regards,
> > Shawn
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: new Tools JIRA project
Posted by Will Glass-Husain <wg...@forio.com>.
Essentially, different developers and different release schedules. The main
Velocity project contains the core engine and has historically been released
at infrequent intervals, while the Tools project has built up a nice
framework around Velocity and has released more often.
WILL
----- Original Message -----
From: "sgtmcd" <sg...@sgtmcd.com>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Sent: Sunday, September 18, 2005 1:15 PM
Subject: Re: new Tools JIRA project
> Will Glass-Husain wrote:
>
>>Hi,
>>
>>What do you think about creating a separate JIRA project for
>>Velocity-Tools? I think I have Karma to do this.
>>
>>The reason is that I'd like to start categorizing all Velocity bugs for
>>different releases. But Tools is on a different release schedule. I
>>think we could move all open Tools bugs by hand (there doesn't seem to be
>>a lot) and skip the import issues.
>>
>>Nathan, Tim, others - comments?
>>
>>Best,
>>WILL
>>
>>
> I don't have a true opinion on this......but I do have a question. why is
> there a velocity-tools project? From a laymens point of view, it seems
> that the projects should be one.
>
> regards,
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: new Tools JIRA project
Posted by sgtmcd <sg...@sgtmcd.com>.
Will Glass-Husain wrote:
>Hi,
>
>What do you think about creating a separate JIRA project for Velocity-Tools? I think I have Karma to do this.
>
>The reason is that I'd like to start categorizing all Velocity bugs for different releases. But Tools is on a different release schedule. I think we could move all open Tools bugs by hand (there doesn't seem to be a lot) and skip the import issues.
>
>Nathan, Tim, others - comments?
>
>Best,
>WILL
>
>
>
I don't have a true opinion on this......but I do have a question. why
is there a velocity-tools project? From a laymens point of view, it
seems that the projects should be one.
regards,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: new Tools JIRA project
Posted by Will Glass-Husain <wg...@forio.com>.
Good idea, thanks. I'm okay with changing release names to "Tools 1.2" and
"Core 1.5". I'll wait for comments from the Tools people.
WILL
----- Original Message -----
From: "Henning P. Schmiedehausen" <hp...@intermeta.de>
Newsgroups: hometree.jakarta.velocity.dev
To: <ve...@jakarta.apache.org>
Sent: Sunday, September 18, 2005 1:19 PM
Subject: Re: new Tools JIRA project
> "Will Glass-Husain" <wg...@forio.com> writes:
>
>>------=_NextPart_000_011E_01C5BC4D.1038D1B0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: quoted-printable
>
>>Hi,
>
>>What do you think about creating a separate JIRA project for =
>>Velocity-Tools? I think I have Karma to do this.
>
> Yes, you have. You are a JIRA admin.
>
> -0. What is wrong/bad with having a category inside the Velocity
> project? Just visibility or any particular reason? IMHO Velocity isn't
> that big a project that we must use multiple projects for it and JIRA
> already has enough different projects.
>
>>The reason is that I'd like to start categorizing all Velocity bugs for =
>>different releases. But Tools is on a different release schedule. I =
>>think we could move all open Tools bugs by hand (there doesn't seem to =
>>be a lot) and skip the import issues.
>
> If that is the main reason, let's add "Tools 1.2" and change "1.4" to
> "Core 1.4" and so on.
>
>>Nathan, Tim, others - comments?
>
> I won't oppose it, but I think it is overkill. In any case you should
> IMHO speak to the infrastructure people.
>
> Best regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
> Linux, Java, perl, Solaris -- Consulting, Training, Development
>
> 4 - 8 - 15 - 16 - 23 - 42
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: new Tools JIRA project
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Will Glass-Husain" <wg...@forio.com> writes:
>------=_NextPart_000_011E_01C5BC4D.1038D1B0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>Hi,
>What do you think about creating a separate JIRA project for =
>Velocity-Tools? I think I have Karma to do this.
Yes, you have. You are a JIRA admin.
-0. What is wrong/bad with having a category inside the Velocity
project? Just visibility or any particular reason? IMHO Velocity isn't
that big a project that we must use multiple projects for it and JIRA
already has enough different projects.
>The reason is that I'd like to start categorizing all Velocity bugs for =
>different releases. But Tools is on a different release schedule. I =
>think we could move all open Tools bugs by hand (there doesn't seem to =
>be a lot) and skip the import issues.
If that is the main reason, let's add "Tools 1.2" and change "1.4" to
"Core 1.4" and so on.
>Nathan, Tim, others - comments?
I won't oppose it, but I think it is overkill. In any case you should
IMHO speak to the infrastructure people.
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org