It doesn't look like I'm going to get this multipart stuff
done by today.  The reason it's been taking so long (5 days
and running now) is because I rewrote the portion of multipart
that does all the parsing. I did that because it was the source
of a few of the more critical file upload bugs, plus it was
difficult to unit test MultipartIterator, which shouldn't have
the parsing logic in it anyway.

But the rewrite took
forever; my intentions were to make a swanky efficient multipart
stream parser and I basically failed to do so.  So I rewrote it
again this morning with less complex code and it seems to do better
unit-test wise, but it's going to take a little more to get some files to
work with browsers for some obscure reason.

Fixing that should 
last me to around the time I have to go to class, and then the
rest of the bug fixing and added documentation will take
the rest of the night. I'm sorry for delaying the release schedule, i'm
trying to make it worth everyone's while.

-----Original Message-----
From: SCHACHTER,MICHAEL (HP-NewJersey,ex2) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 05, 2002 8:46 AM
To: 'Struts Developers List'
Subject: RE: The missing release plan


definately 2. i've been having a terrible time with multipart
stuff, i'll still be working on it throughout the day.

-----Original Message-----
From: Martin Cooper [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 05, 2002 1:18 AM
To: Struts Developers List
Subject: The missing release plan


Through informal discussion, we decided to go to Struts 1.1 Beta 1 on March
4th, which is today. However, I've realised that I dropped the ball, and did
not produce a release plan, to be voted on by the committers. So the
question is, how should I best recover?

Here are a couple of options:

1) Continue with a Beta 1 release in the next day or so, regardless of a
vote on the release plan, but depending on when the crucial fixes are
checked in.

2) Post a release plan ASAP, and await a "go" vote before proceeding with
the Beta 1 release.

Other suggestions are welcome.

Committers, please let me know what you would like me to do in this respect.

--
Martin Cooper



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

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

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

Reply via email to