I've now tested the applications with the legacy RP and updated the Release Notes as to the new "Opt-In Cancel Handler".
As this point, I'd rather not update the legacy RP to support Opt-In Cancel Handling. If we make any further changes to this feature, or any other new feature, we'd have to maintain the code in two places. As long as the behavior gracefully degrades, it seems reasonable to me to add new features to the new RequestProcessor and leaving the legacy RP alone (unless the 1.2.x branch is also going to be released - but no one has volunteered to do that). If people want access to features new to 1.3, they can use the new RP. If the new CRP passes muster and remains the default for 1.3.1, we should move the legacy RP to "extras" and deprecate it. If this change prompts anyone to change their vote, please chime-in now. A release plan is a majority vote, so we need three binding +1s from PMC members and more binding +1s than -1s. A +1 here is on the tagging the repository. A quality vote would follow once the test builds are posted. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
