Gary Winiger wrote: > And the Release Binding is? How about Major?
In this case, why would Major be a requirement? (he asks naively, trying to inject architectural clarity into this type of conversation...) Personally, I see nothing in this case that would require a major release. It makes no incompatible changes to existing interfaces, so, by the rules in the interface/release taxonomies, it should qualify for patch binding. It may not follow all the best practices and policies, but I'm not sure how that compliance maps to the release taxonomy.... Am I missing something? -John
