--- On Wed, 11/26/08, Musachy Barroso <[EMAIL PROTECTED]> wrote: > If there is a change that breaks backward compatibility, like: > > https://issues.apache.org/struts/browse/WW-2655 > > how does it get tracked so it lands in the "Backward compatibility > issues with previous versions" section of the release notes?
I'm also curious, since the change for the includeParams thing could break compatibility. I don't see a way to tag JIRA issues like Confluence pages. One option, I guess, would be to create a "compatibility issues" issue and link breakers to it and pull those out somehow, but that seems a little hacky. IIRC we can add arbitrary flags for inclusion in the issues--maybe we could add a "incompatibility" flag and mark them that way? Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
