In all likelihood, as soon as you get around to handling this, we may have applied some other small patches (like finishing putting the action property on the rest of the tags), and we will be ready to pop-out another milestone.
Moving forward, I think we should let the state of the CVS decide when it's time for another release. If any of us post a patch that needs to get out into the hands of production teams, then we should roll a release. Those numbers between the dots are integers, and we should treat them as such =;0)
It's important to remember that a release is a majority vote. Any one of us can tag the CVS and roll a release whenever we like. All it takes to get it out the door is three binding +1's and more positive votes than negative votes. So, release *.* can be ready whenever you are =:0)
On a related note, the one thing we should be careful about is allowing product changes that would foil a release. The Commons Resource initiative (which I support, use, and will continue to help with) is a good example. I would be leery of moving the main trunk over to Commons Resources until C/R is out of the sandbox and ready for beta. I would especially insist that any other product changes be released before making a dependency change, lest innocent bystanders get stuck behind unexpected issues. (Been there, did that, won't let it happen again.)
But, as far something like this goes, make the fix, and I'll help roll the release =:0)
-Ted.
Arron Bates wrote:
-0
Only because there is a bug raised against the nested tags where it's dropping a reference for included/tiles files in some strange instance.
I would have liked to have confirmed, patched and squished/handled it, but my last few weeks have been crazy with moving to the US. I wont be able to get onto it until thurday next week until after the move. Would be sweet if 1.1 could wait until then, but anyways.
Just need to say that a version cut now is done with possible issue.
Anyone's welcome to dive in there and have a play to see if it is an issue...
With obvious other priorities, I'll probably just gruble a little and wait to have it handled for 1.2 or 1.1.1 :P
Arron.
Ted Husted wrote:
Since no significant issues have arisen in response to Struts 1.1 RC2, I propose that we release the tip of the main trunk in CVS as the Struts 1.1 Final release. I have checked in a proposed release plan, which is available for review on the Struts web site:
http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
Release plans must pass by a majority vote of committers on the project, but all other interested parties are welcome to cast their votes (and/or make comments or suggestions on the plan) as well.
-------------------------------------------------------------------------- Vote: Struts 1.1 Final Release Plan [ ] +1 I am in favor of the release, and will help support it [ ] +0 I am in favor of the release, but am unable to help support it [ ] -0 I am not in favor of the release [ ] -1 I am against this proposal (must include a reason). -------------------------------------------------------------------------
I am +1 on the Struts 1.1 Final release plan.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
