I think it's fair to look at 1408 & 1409... they need to be fixed in trunk, as 
well, but it would be nice for them to be fixed for 5.2 users in the meantime. 
I looked over the revised date picker, but still evaluating; it'll be later 
tonight before I can make sure it's really correct.

Also, TAP5-1549 would be nice to fix for both trunk and 5.2. I was planning on 
tackling that one, as well.
And maybe TAP5-1548. 

Those two were issues that I found when upgrading a large, functioning 5.1.0.5 
app to 5.2.5; they caused me a lot of grief, and it'd be nice to get them fixed 
so others don't have similar issues. That said, TAP5-1548 still has a decent 
amount of time left in the issue, at least for me.  I can reproduce the issue 
reliably and know how to work around it, but I haven't yet tracked down the 
exact source of the problem.  What timeline are you thinking of for trying to 
release 5.2.6?

Robert



On Jun 21, 2011, at 6/214:33 PM , Howard Lewis Ship wrote:

> I'm backporting some fixes for a client to 5.2.  I expect to have a
> 5.2.6 release ready very soon.  Anything critical that needs to go
> into it beyond the Prototype/JS stuff I've been doing?
> 
> -- 
> Howard M. Lewis Ship
> 
> Creator of Apache Tapestry
> 
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
> 
> (971) 678-5210
> http://howardlewisship.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Reply via email to