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 2004/12/15 19:44:16 UTC
priorities - call for discussion
Hi,
As a new committer, I'm getting ready to dive into the repository. I checked Bugzilla this morning -- there's 142 open issues. There's a lot of stuff to do, and I'm asking for help.
***
First, I'd like to open a discussion on priorities. What are the most important bugs/issues to resolve? We can discuss on the list, but I thought it'd be helpful to keep a running list on the Wiki:
http://wiki.apache.org/jakarta-velocity/IssuePriorities
It'd be great if we could list out the unresolved issues that are the most important. You can informally vote for an issue by adding your initials to the "Priority" column. We should be able to make rapid progress in the "Bug" and "Enhancements - Basic" sections.
Incidentally, here's some thoughts on how you can get your submitted patch committed. (All these Wiki pages are in draft form -- I'd welcome any comments).
http://wiki.apache.org/jakarta-velocity/GettingYourPatchCommitted
***
The second discussion is on a RoadMap. I'd like to see a release that captures some of the backlog of bug fixes/enhancements. My personal opinion is that we should commit as much of the backlog as possible, provided it fits with the core vision of Velocity. Maintaining compatibility for users of old versions has been paramount up to this point. We need to continue that philosophy for at least another release.
Following 1.5, should we aim for a version 2.0 that relaxes the compatibility requirement? I've a big bias against massive version 2.0 rewrites -- they're very difficult to complete. But incrementing the major version number would allow us to make non-compatible changes to the language that improve usability. An example might be changing the way Velocity handles white space to be less confusing.
I've put a few basic comments here. What does everyone else think?
http://wiki.apache.org/jakarta-velocity/RoadMap
***
The third discussion is on openness and communication. I hate it when an idea or issue gets put out there and nobody responds. I'd like to suggest all of us make a point on providing feedback to new ideas and for the committers to provide feedback on how a submitter can get his/her patch committed. Three committers isn't quite enough. Maybe we can get some new committers in the next 3-6 months from the pool of active contributors.
Looking forward to everybody's thoughts. Let me know if this seems like a good process.
Best,
WILL
Re: tests - should they be in the Jar file?
Posted by Nathan Bubna <nb...@gmail.com>.
I agree it isn't a big deal as they are small, but i also don't
believe they belong in the release jar.
On Thu, 16 Dec 2004 08:12:48 -0800, Will Glass-Husain <wg...@forio.com> wrote:
> Hi Shinobu,
>
> A quick response to your question on tests...
>
> > One thing that's bothering me about the tests is the source tree.
> > Couldn't we separate it from the build tree? I'm sure we don't need
> > the test classes in the release jar.
>
> I don't personally have strong feelings on this, other than apathy re:
> changing what is working fine. There's a convenience of everything being
> together, and I don't really see a downside to it being in the release Jar.
> (The size is small, and there's no side effects). Are there other comments
> on this?
>
> Best,
> WILL
>
> ----- Original Message -----
> From: "Shinobu Kawai" <sh...@gmail.com>
> To: "Velocity Developers List" <ve...@jakarta.apache.org>
> Sent: Thursday, December 16, 2004 5:32 AM
> Subject: Re: priorities - call for discussion
>
> > Hi Will,
> >
> >> Incidentally, here's some thoughts on how you can get your submitted
> >> patch committed. (All these Wiki pages are in draft form -- I'd welcome
> >> any comments).
> >> http://wiki.apache.org/jakarta-velocity/GettingYourPatchCommitted
> >
> > Great page! I'll get to my tests when I have enough time. ;)
> >
> > #*
> > One thing that's bothering me about the tests is the source tree.
> > Couldn't we separate it from the build tree? I'm sure we don't need
> > the test classes in the release jar.
> > *#
> >
> > Best regards,
> > -- Shinobu Kawai
> >
> > --
> > Shinobu Kawai <sh...@gmail.com>
> >
> > ---------------------------------------------------------------------
> > 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
Fwd: tests - should they be in the Jar file?
Posted by Shinobu Kawai <sh...@gmail.com>.
Oops, I forgot to reply to the list. ;)
---------- Forwarded message ----------
From: Shinobu Kawai <sh...@gmail.com>
Date: Sat, 18 Dec 2004 00:43:39 +0900
Subject: Re: tests - should they be in the Jar file?
To: Will Glass-Husain <wg...@forio.com>
Hi Will,
> > One thing that's bothering me about the tests is the source tree.
> > Couldn't we separate it from the build tree? I'm sure we don't need
> > the test classes in the release jar.
>
> I don't personally have strong feelings on this, other than apathy re:
> changing what is working fine. There's a convenience of everything being
> together, and I don't really see a downside to it being in the release Jar.
> (The size is small, and there's no side effects). Are there other comments
> on this?
## I definitely need to work on my writing skills.
Actually, it isn't the fact that the tests are in the jar file that's
bothering me. In the broadband age, what's another couple megabytes?
If something would bother me with the test classes being in the jar,
it would be because they don't work without the test files which are
not bundled in the jar.
Anyways, what I really wanted, is the test sources in a different
directory. It's more of a philosophical issue for me, I guess. The
other ASF projects I've messed with (Tomcat, Struts, Maven, Commons,
etc.) all have separate source trees for the product and the tests. I
might just have to get used to it. (Believe me, it took me quite a
while to get used to the "Brackets should begin and end on a new
line." coding standard. ;))
Best regards,
-- Shinobu Kawai
--
Shinobu Kawai <sh...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
RE: tests - should they be in the Jar file?
Posted by Tim Colson <tc...@cisco.com>.
> Just a comment that small is relative.
> In 1.3.1, the tests are 16% of the jar file (56K).
Hmm... Mike just changed my mind. I thought they were only about 4K... but
~50K is worth removing. I just looked at my latest compiled test dir and it
seems to be about 120K. Yeah, that's worth excluding from the release jar, I
think.
Anecdotally - I am more wary of "large" libs, not due to bandwidth, but they
make me nervous because of the potential for increased complexity... which
might blow up. Small libs, however horribly they may be written, lull me
into a warm fuzzy sense of complacency, much like a puppy. "Ooooh, only 45
Kilobytes... how cute! How much damage could that do?"
-Timo
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: tests - should they be in the Jar file?
Posted by Mike Kienenberger <mk...@alaska.net>.
Will Glass-Husain <wg...@forio.com> wrote:
> I don't personally have strong feelings on this, other than apathy re:
> changing what is working fine. There's a convenience of everything being
> together, and I don't really see a downside to it being in the release
Jar.
> (The size is small, and there's no side effects). Are there other
comments
> on this?
Just a comment that small is relative.
In 1.3.1, the tests are 16% of the jar file (56K).
If velocity is used as part of a java applet being downloaded over a modem,
then it's more signficant than if it's sitting on your server with 160Gb of
disk space free.
For my own use cases, this makes no difference. Apathy is probably good
enough as long as the tests remain small, and the tests don't require any
bundled dependencies.
In the modem case above, a user could always downsize the velocity jar file,
removing the test code.
-Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
RE: tests - should they be in the Jar file?
Posted by Tim Colson <tc...@cisco.com>.
> > One thing that's bothering me about the tests is the source tree.
> > Couldn't we separate it from the build tree? I'm sure we don't need
> > the test classes in the release jar.
> (The size is small, and there's no side effects). Are there
> other comments on this?
Doesn't bother me much either, especially since it's only a few kilobytes.
But I agree that it's also not absolutely necessary in the release jar. If
somebody put in a patch to not include those test classes during the ant
build process, that'd be fine. No big improvement of course, but no problem
either.
Timo
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
tests - should they be in the Jar file?
Posted by Will Glass-Husain <wg...@forio.com>.
Hi Shinobu,
A quick response to your question on tests...
> One thing that's bothering me about the tests is the source tree.
> Couldn't we separate it from the build tree? I'm sure we don't need
> the test classes in the release jar.
I don't personally have strong feelings on this, other than apathy re:
changing what is working fine. There's a convenience of everything being
together, and I don't really see a downside to it being in the release Jar.
(The size is small, and there's no side effects). Are there other comments
on this?
Best,
WILL
----- Original Message -----
From: "Shinobu Kawai" <sh...@gmail.com>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Sent: Thursday, December 16, 2004 5:32 AM
Subject: Re: priorities - call for discussion
> Hi Will,
>
>> Incidentally, here's some thoughts on how you can get your submitted
>> patch committed. (All these Wiki pages are in draft form -- I'd welcome
>> any comments).
>> http://wiki.apache.org/jakarta-velocity/GettingYourPatchCommitted
>
> Great page! I'll get to my tests when I have enough time. ;)
>
> #*
> One thing that's bothering me about the tests is the source tree.
> Couldn't we separate it from the build tree? I'm sure we don't need
> the test classes in the release jar.
> *#
>
> Best regards,
> -- Shinobu Kawai
>
> --
> Shinobu Kawai <sh...@gmail.com>
>
> ---------------------------------------------------------------------
> 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: priorities - call for discussion
Posted by Shinobu Kawai <sh...@gmail.com>.
Hi Will,
> Incidentally, here's some thoughts on how you can get your submitted patch committed. (All these Wiki pages are in draft form -- I'd welcome any comments).
> http://wiki.apache.org/jakarta-velocity/GettingYourPatchCommitted
Great page! I'll get to my tests when I have enough time. ;)
#*
One thing that's bothering me about the tests is the source tree.
Couldn't we separate it from the build tree? I'm sure we don't need
the test classes in the release jar.
*#
Best regards,
-- Shinobu Kawai
--
Shinobu Kawai <sh...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: introduction
Posted by Christian Trutz <ch...@smilebase.org>.
Hi Will,
> I think most people set the encoding in the Java code when merging
> the template.
ok thats right, but if you have a multi-language application where Unicode
isn't allowed, and you have multiple templates in multiple encodings ... an
encoding configiguration is perhaps usefull. But i think such an enhancement
should have low priority ...
The solution in Bugzilla is a little "overloaded" but the requirement is
usefull ...
Chris
On Wed, 15 Dec 2004 13:38:57 -0800, Will Glass-Husain wrote
> I haven't heard a big demand for this feature, myself.
>
> (Velocity templates should be able to specify their own encoding)
>
> I think most people set the encoding in the Java code when merging
> the template.
>
> WILL
>
> ----- Original Message -----
> From: "Christian Trutz" <ch...@smilebase.org>
> To: "Velocity Developers List" <ve...@jakarta.apache.org>
> Sent: Wednesday, December 15, 2004 1:08 PM
> Subject: introduction
>
> > Hello velocity community,
> >
> > my name is Christian Trutz (from Bonn/Germany) and I am a enthusiastic
> > velocity user! I thing the Apache way of developing software is a good
> > one,
> > and I would be proud making velocity step by step a little better :-)
> >
> > I think #24796 is a usefull enhancement but
> >
> > ## encoding = foo
> >
> > is a little strange for me. I think encoding is a meta data of the
> > template/file which should not be specified in the file.
> >
> > chris
> >
> > ---------------------------------------------------------------------
> > 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
--
Christian Trutz
Tel.: 0228 2421689
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: introduction
Posted by Will Glass-Husain <wg...@forio.com>.
I haven't heard a big demand for this feature, myself.
(Velocity templates should be able to specify their own encoding)
I think most people set the encoding in the Java code when merging the
template.
WILL
----- Original Message -----
From: "Christian Trutz" <ch...@smilebase.org>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Sent: Wednesday, December 15, 2004 1:08 PM
Subject: introduction
> Hello velocity community,
>
> my name is Christian Trutz (from Bonn/Germany) and I am a enthusiastic
> velocity user! I thing the Apache way of developing software is a good
> one,
> and I would be proud making velocity step by step a little better :-)
>
> I think #24796 is a usefull enhancement but
>
> ## encoding = foo
>
> is a little strange for me. I think encoding is a meta data of the
> template/file which should not be specified in the file.
>
> chris
>
> ---------------------------------------------------------------------
> 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
introduction
Posted by Christian Trutz <ch...@smilebase.org>.
Hello velocity community,
my name is Christian Trutz (from Bonn/Germany) and I am a enthusiastic
velocity user! I thing the Apache way of developing software is a good one,
and I would be proud making velocity step by step a little better :-)
I think #24796 is a usefull enhancement but
## encoding = foo
is a little strange for me. I think encoding is a meta data of the
template/file which should not be specified in the file.
chris
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org