As for the Release Plan, we can continue to amend the B3 page. When we're ready for R1, make the final revisions and re-post it under a new name. Since everything should be done by then, the freeze date can be set for +(72 hours), to coincide with the close of the vote.
At this point, I just don't have any more blood to shed for 1.1. If we can't get this thing out the door in February, then we should look for some more comitters who can.
Either way, come March, I say it's time to get a fresh, test-first-design start on 2.x. A year of FUD is more than enough.
-Ted.
Martin Cooper wrote:
Ted had suggested that we resolve the outstanding items first, and then put together a release plan, complete with tag date. See:http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=612913 However, I don't believe that's working. In fact, as I believe Ted himself said of the 1.1-b3 drive, having a date to aim for is a better motivator. Unfortunately, as I mentioned before, I don't have much time to help kill outstanding bug reports for RC1, due to current "day job" pressures. It'd be great to see an RC1 on or around Feb 14th, and I can do the RM thing, but I'm going to have to rely on others of you to get us ready for that.Also, what is the status of the idea of separating the contrib libraries out of the release? I'm not certain what the result was of any vote on this, but I had the impression there wasn't enough response to make a decision.IMO, Struts-EL should stay put until we get Struts 1.1 out the door. After that, we can discuss how to incorporate contrib code into the release as part of a broader discussion of how to factor distributions. -- Martin Cooper
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
