On Wed, Nov 24, 2010 at 11:07 AM, sebb <seb...@gmail.com> wrote: >> A major version change requires that you change the package name (the >> part that comes after org.apache.commons) and the Maven artifactId to >> the component's name with the major version appended to the end. >> >> [ ] +1 - accept this as a rule >> [X] -1 - do not accept this as a rule > > Components should be allowed to increment the major version even if > there is no binary incompatibility. > > A package name change forces total binary incompatibilty. >
Please keep in mind that this "rule" is made to be able to be broken for the special cases. It's intended to be in place for the general case, which most components/releases would fall under. This is to avoid having to argue this same point all the time. We all have better things to do. If we can just say "you break the version/package/artifact rule" with this release (and point to the Wiki page), then there really is no discussion, unless the component feels that it is in a special case. Also, the [VOTE] thread could have the justification in it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
