On 3/26/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Good thoughts.
There's a few interesting Texen improvements in JIRA. Making Texen a
separate project will be motivating to get those committed. I like
the idea of doing a 1.0 release on the current (post-migration) code
base, then adding new features.
For completeness, I'd like to see us do a release of DVSL as well.
I'll help with all this.
The "treat arrays like lists", "support iterables", "support vararg"
also seem good improvements on usability. Are all these items in
JIRA?
they are now.
WILL
On 3/26/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
> On 3/25/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
> > Colleagues,
> >
> > What should we aim for with Velocity 1.6?
> >
> > I feel that we've cleaned up most urgent bugs and pressing issues with
> > the 1.5 release. Given the sporadic nature of our development
> > efforts, timelines are a little risky. Still, I was thinking it'd be
> > nice to do a release of 1.6 this fall.
>
> if not before. :)
>
> > JIRA lists 38 issues with a 1.6 target. There's a few bugs and a lot
> > of incremental feature suggestions, few with actual code. Many of
> > these enhancement requests will likely get bumped back unless someone
> > champions them.
> >
> >
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310104&fixfor=12310290
> >
> > What issues do our committer and developer community care about?
>
> the ones they work on. :) myself, i'm interested in helping to pull
> out Texen, do a 1.0 release immediately after the move, and then start
> improving it. also, i'm thinking about setting aside some time to
> work on a way to make Velocity treat lists and arrays as much like
> fixed-length lists as possible, so that template authors needn't
> bother about the difference. and yeah, i think that can be done in a
> B.C. manner.
>
> oh, i'm also interested in exploring ideas for supporting Iterable in
> #foreach and varargs in method calls (i.e. key JDK 1.5 improvements)
> without the need to resort to stuff on the whiteboard. JDK 6 is out
> and many companies (mine included) now dev against 1.5. I'd like to
> see these supported out-of-the-box, if at all possible.
>
> > I think we should have modest goals. Myself, I mostly want to see the
> > macro issues addressed. I'd also like to clean up the project, split
> > out Texen and Anakia (per Henning's suggestions on maintaining
> > compatibility). I've written up a few notes at
> > http://wiki.apache.org/velocity/RoadMap
> >
> > If one of the committers (Henning?) becomes fired up, we could start a
> > 2.0 branch, though I confess that personally I'm more interested in
> > incremental development.
>
> for the moment, i am too. it's currently only the whitespace stuff
> that makes me itch to move on to 2.0...
>
> > WILL
> >
> >
> >
> >
> >
> >
> > --
> > Forio Business Simulations
> >
> > Will Glass-Husain
> > [EMAIL PROTECTED]
> > www.forio.com
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
---------------------------------------------------------------------
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]
