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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]>
> To: "Velocity Developers List" <velocity-dev@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: [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