http://tinyurl.com/ysx3x
Six have patches, which I will try to apply tomorrow. Most of the others are reports about problems I may not know how to fix.
I can thing of four ways to deal with these:
(1) mark reports without proposed solutions "enhancements" (2) mark unresolved problem reports LATER (like before) (3) change the release plan so we can leave them open (4) forgo the release indefinitely
On a related topic, would anyone call any of these "showstoppers".
-Ted.
Ted Husted wrote:
I've amended the date on the (now venerable) 1.2.0 release plan for this weekend.
http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
I believe the release notes are in good shape now. I already marched through most of the stale 1.0/1.1 tickets, and can mop up the rest in short order. I imagine there will be a few patches that we can apply, but I've carved out some time to work on such.
Note that I've left room in the release plan for the idea of multiple managers. If someone were up for sheparding the tests, especially the example application testing, I'd welcome the help. Someone else could also sign up for the final tag, roll, and announce part of the job. Of course, if everyone is busy, I'll be happy to muddle through on my own. :)
Since this is a x.0 release, the plan calls for a majority vote.
Here's my +1
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
