I took advantage of Tuesday at ApacheCon Hackathon to submit patches for a
couple of JIRA issues - one small, one larger.  The small one was committed
right away (with some modification) - thanks IGOR!!.  (Or 10x, your new
favorite saying).

Anyway, the other one was shelved, also by Igor, saying that this was
something that would be addressed in 1.5.  This was a little frustrating
because that was the one I spent more time on, and sitting next to Martijn,
he gave it a cursory glance and thought it could go in 1.4....   But I have
no way of knowing whether it can go in or not.  It's not API breaking, so I
thought it could go in, too.

So - I'm sitting here with Bruno Borges, and we'd love to knock out some
issues, but neither of us wants to waste any time on issues that won't be
fixed.  How do we know, out of the 191 currently unresolved issues against
wicket-core, which we can work on, that aren't being worked on, and will be
accepted in the current version?

Thanks!

-- 
Jeremy Thomerson
http://www.wickettraining.com

Reply via email to