DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15196.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15670.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15670.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Wed, 25 Dec 2002, Ted Husted wrote:
12/24/2002 6:53:29 PM, Martin Cooper [EMAIL PROTECTED] wrote:
The plan doesn't say we're committing to fixing the problem, it
says the problem report must be resolved before final release of
Struts 1.1. I believe we need to do that, even if we have to
Craig's message mentions an up to the minute list, which I
believe should be a Bugzilla query.
If something comes in just before the freeze, and it's not a true
show stopper, we can just make it LATER, which we should be doing
anyway.
I would just like to get out of the habit of dual
On Thu, 26 Dec 2002, Ted Husted wrote:
Date: Thu, 26 Dec 2002 16:55:34 -0500
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: [VOTE] Struts 1.1 Beta 3 Release Plan (revised)
Craig's message
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15673.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Ok, I'll update the Roadmap and the B3 plan with the appropriate
queries, and add a box next to the bugs we are swatting to indicate
their status. This will at least make the static list easier to maintain
=:0)
Just finished setting a bunch of new equipment, and I'm quite ready to
get back to
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15673.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15673.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
husted 2002/12/26 17:49:41
Modified:doc status.xml
Log:
Add link from Roadmap to 1.1b3 proposal. Add Bugzilla links to proposal. Mark items
that have already been resolved yeah!/.
Revision ChangesPath
1.20 +25 -29jakarta-struts/doc/status.xml
Index:
husted 2002/12/26 17:49:54
Modified:doc/proposals release-plan-1.1b3.xml
Log:
Add link from Roadmap to 1.1b3 proposal. Add Bugzilla links to proposal. Mark items
that have already been resolved yeah!/.
Revision ChangesPath
1.4 +52 -22
husted 2002/12/26 17:53:59
Modified:doc/proposals release-plan-1.1b3.xml
Log:
Insert #13645 to b3 bug list, as discussed.
Revision ChangesPath
1.5 +7 -1 jakarta-struts/doc/proposals/release-plan-1.1b3.xml
Index: release-plan-1.1b3.xml
dmkarr 2002/12/26 18:23:52
Modified:contrib/struts-el README.txt
Log:
Removed present and notPresent from the list of tags in the logic library
that were NOT ported to struts-el. I forgot to remove them from this list
after I implemented them later (because I realized the
husted 2002/12/26 18:38:43
Modified:doc/userGuide index.xml
Log:
Update index with current section numbers.
Revision ChangesPath
1.24 +4 -2 jakarta-struts/doc/userGuide/index.xml
Index: index.xml
On Thu, 26 Dec 2002, Ted Husted wrote:
Ok, I'll update the Roadmap and the B3 plan with the appropriate
queries, and add a box next to the bugs we are swatting to indicate
their status. This will at least make the static list easier to maintain
=:0)
I just updated the site with your
I don't really think we need a revote, but if others do you can count in
my +1. At this stage, I'm all for marking new bugs as LATER for the
next release (whether that be a beta or final). By all means, let's
try to knock out the bugs we can between now and the time the beta is
cut, but
17 matches
Mail list logo