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 2006/10/01 02:05:32 UTC
Re: Velocity Hackathon - October 9/10
All the known bugs, of course.
We might release if a couple of bugs remain stubbornly unfixed, but I'd like
to get most done. We've fixed dozens since 1.4. It'll be a pleasure to stop
telling users who report the same problem for the umpteenth time "use the
source control head, it's fixed" or "this is a known issue, we'll get to it
eventually".
WILL
On 9/30/06, Nathan Bubna <nb...@gmail.com> wrote:
>
> On 9/29/06, Will Glass-Husain <wg...@forio.com> wrote:
> > Hi Malcolm,
> >
> > I think we'll be close. (But I'll confess I've gotten in trouble
> > every time I've made a prediction).
> >
> > My current feeling is that at ApacheCon we can work together to update
> > the docs, put the outstanding enhancement issues in, and fix a bunch
> > of the bugs. Then we can issue a "feature-complete beta2" right in
> > mid-October.
> >
> > I've got this perfectionist zeal to fix all the bugs before releasing.
> > I count 17 without patches right now. If other community members
> > could step up and tackle one or two each, we could get them all done.
>
> All the bugs? or all the known bugs? :)
>
> > Once those are fixed, we would do a "Release Candidate 1", wait a
> > couple of weeks, and if all is well issue Velocity 1.5.
> >
> > (one key criteria for success of RC1 would be backwards-compatibility
> > with other frameworks like Click and Cayenne-- look forward to your
> > feedback on that).
> >
> > Henning, Nathan, seem about right?
>
> Yeah, i'd like to see these all fixed too. But for the record, if we
> fail to squash some of the obscure ones that have been around for a
> few releases already, i'd still like to see a release happen. There
> have been too many improvements to hold this back much longer.
>
> > WILL
> >
> > On 9/29/06, Malcolm Edgar <ma...@gmail.com> wrote:
> > > Hi Will,
> > >
> > > do you think a 1.5 release is achievable in mid October. I reason I
> > > ask is Click Framework 1.0 is about to be release, but it would be
> > > worth delaying a few weeks to include Velocity 1.5.
> > >
> > > regards Malcolm Edgar
> > >
> > > On 9/30/06, Will Glass-Husain <wg...@forio.com> wrote:
> > > > Hi,
> > > >
> > > > We're holding a mini 'hackathon' for Velocity at ApacheCon October 9
> &
> > > > 10. Henning and I will be there, though we welcome participation
> from
> > > > others at the con or remotely. I'm looking forward to the focused
> > > > time together.
> > > >
> > > > I'd like to challenge us to ready ourselvesfor a release right after
> > > > ApacheCon. I've grouped the open items below. I'll take personal
> > > > responsibility to see that issue below with a submitted patch that
> is
> > > > ready (or almost ready) makes it in. Many of those are mine,
> anyway.
> > > >
> > > > The remaining bugs are all fairly subtle. They seem to be grouped
> > > > around escaping issues, macro issues, and error reporting issues.
> > > > With a little luck we can work through most of them. If anyone
> wants
> > > > to dive into the code and work through a few, that'd be fabulous.
> > > >
> > > > Two specific items we could use help on. Anyone a Texen or DVSL
> guru?
> > > > VELOCITY-413 (DVSL) really needs to be fixed. And there's a nice
> > > > Texen patch (VELOCITY-422) waiting to be added.
> > > >
> > > > Cheers,
> > > >
> > > > WILL
> > > >
> > > >
> > > >
> > > > Bugs (has patch/partial patch)
> > > > ---
> > > > VELOCITY-132 IllegalArgumentException while calling an overloaded
> method
> > > > (needs a little work)
> > > >
> > > > Bugs (no patches)
> > > > ---
> > > >
> > > > VELOCITY-449 Velocity Uberspector behaves differently for
> get(String)
> > > > and put(String, Object) methods
> > > > VELOCITY-456 Uberspector chokes on a number of corner cases
> > > > VELOCITY-458 InternalContextBase defines non-serializable
> non-transient fields
> > > >
> > > > VELOCITY-71 False positive error condition parsing
> VM_global_library.vm
> > > > VELOCITY-82 VM libs will not autoreload if unparseable at
> Velocity startup
> > > >
> > > > VELOCITY-214 References to non-public members (inner classes,
> fields,
> > > > etc.) should log a warning rather than failing silently
> > > > VELOCITY-251 $\!{foo} doesn't render as expected
> > > > VELOCITY-264 Escaping in form of "$\!{foo}" does not work
> > > > VELOCITY-280 Parsing of braces after a reference fails
> > > > VELOCITY-209 Encountered ")" Was expecting one of: ")"
> > > >
> > > > VELOCITY-24 calls to local macros not always made when template
> caching is off
> > > > VELOCITY-262 #set not parsed in #macro
> > > > VELOCITY-285 reference within macro and foreach is incorrect
> > > > VELOCITY-435 ParseErrorException not thrown with #macro parse
> error
> > > >
> > > > VELOCITY-455 Error in chapter "Escaping VTL Directives" in the
> User Guide
> > > > VELOCITY-457 documentation mistake? order of Velocimacros in
> template
> > > >
> > > > VELOCITY-413 DVSL doesn't appear to work with Velocity 1.5
> > > >
> > > >
> > > > Enhancements (with patches/partial patches)
> > > > ---
> > > > VELOCITY-405 Document new Event Handler features (needs work from
> WGH)
> > > > VELOCITY-423 Report invalid references (needs work from WGH)
> > > > VELOCITY-179 Prevent execution of methods on Class, ClassLoader and
> > > > related classes (needs work from WGH)
> > > >
> > > > VELOCITY-422 Add support for <property> and <propertyset> nested
> > > > elements to TexenTask.
> > > >
> > > > VELOCITY-414 Extend the MethodInvocation exception to be able to
> give
> > > > the velocity macro writer a usefull error page
> > > > (needs work)
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > >
> > >
> >
> >
> > --
> > Forio Business Simulations
> >
> > Will Glass-Husain
> > wglass@forio.com
> > www.forio.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
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com