This is why I keep stuff that I want to move on a self-interested/aggressive path not at Apache. What’s here needs to consider the best interest of all users.
If you’re basically going to make the next version incompatible for anyone who upgrades because you need something I don’t think that’s acceptable. I think taking some liberties is fine if you’ve contributed a ton, but if every user of the assembly plugin is going to get punched in the face when they upgrade to the only available next version I think that’s pretty crappy. You should fork it and make your client use your fork, it should be your problem not every users problem because you need an expedient fix. I hold on to spot fixes for customers for months until I can find a way to make it work generally or I just maintain the fork. > On Jul 14, 2015, at 11:15 AM, Benson Margulies <[email protected]> wrote: > > I have selfish/professional reasons to desire a release with a fix to > MASSEMBLY-777, and the fix, involving an intentional incompatibility, > needs to be 3.0.0, and, anyhow, the pom is all set up for 3.0.0 to be > next. So I plan to start the process tomorrow morning EDT unless > someone objects. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
