Date: 2004-10-31T00:10:00
   Editor: EddieBush <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: EddieBush
   URL: http://wiki.apache.org/struts/EddieBush

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -31,7 +31,7 @@
 
 * [http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31230 31230] - Multiple classes 
using deprecated DefinitionsUtil class - Patch to DefinitionDispatcherAction could be 
considered, and the rest tabled for 1.3.
 
-* [http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31501 31501] - html:form focus 
generates non-XHTML - Could be invalid 
+* '''[http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31501 31501]''' - html:form 
focus generates non-XHTML - Could be invalid 
 
 * [http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31642 31642] - <bean:include> 
always include Session id (if any) even for external Urls (href attribute) - Patch 
could be considered 
 
@@ -42,20 +42,7 @@
 * [http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31827 31827] - Bug in validation 
part - Could be a support issue
 
 = Thought-Holder =
-== Follow-up to Ted's Post ==
-
-Are there any glaring inconsistencies in the posted documents with the Tomcat release 
philosophy?
-
-== Release Thoughts ==
-
-So ... according to the release plan we're over-due a vote?  Actually, that's getting 
the cart before the horse, isn't it?  What about bugzilla?  We still need to address 
that, don't we?  Most everything there is an enhancement.  There are a few issues, 
but, IMHO, nothing we're going to solve before this release gets cut.
-
-Are there any show stoppers for anyone?
-May we proceed to defer outstanding issues to 1.2.6?  ... or are we moving on to 1.3? 
 I need to look at the roadmap I suppose an get a feel for what our current direction 
is.
-
-In any case, it seems to me bugzilla has yet to be dealt with and needs to be.  From 
there, as I understand it, there should be a build made that we all test as thoroughly 
as we can - and vote on.  I agree with your earlier statement about not voting +1 
unless you have the utmost confidence in the build from having battle-tested it, that 
is, provided quorum may be reached with those who can't battle-test abstaining from 
the vote.  In the end, however, it's up to each of us to vote our conscience, 
regardless of whether or not we can battle-test.
-
-If that's unintelligible, I claim sleep-deprivation! :-)
 
+(Empty)
 ----
 CategoryHomepage

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to