Andrew McIntyre wrote: > On 7/21/06, Rick Hillegas (JIRA) <[email protected]> wrote: > >> Detaching this issue from 10.3. Fixing it seems to require changing >> the non-ANSI behavior of implicit and explicit casts. Changing this >> behavior probably will affect existing applications and it seems to be >> the sort of fix which we need to defer to a major release. That is, this >> is appropriate for 11.0 but not 10.3. > > > Would it be useful to have an 11.0 in JIRA to track these sorts of changes?
Not sure, in this case I'm not convinced an 11.0 release would be required to support BOOLEAN, even with the fixed casts. I don't think any real analysis was done of the potential impact to real applications. It maybe also that the changes in the trunk drive the version number, not the other way around. If someone contributes some feature that the community believes requires the version change should happen, then the trunk would be bumped to 11.0. Adding 11.0 now is just going to raise questions of when is the 11.0 release compared to the 10.3 release, and how do I develop for the 11.0 release if the next release is 10.3? Dan.
