For me, breaking source compatibility should be limited to what can be adjusted to in my sources very easily. I would also consider whether the breaks are for a cosmetic reasons for an actual bug fix. I would probably pass on cosmetic breaks within minor releases.
In this case, an exception declared unnecessarily can make client code more cumbersome, but not always, if other parts of the code happen to throw the same exception. More important is binary compatibility, which we should not break within minor releases. What happens in this case to BC? Gary On Mon, Jan 15, 2018 at 2:26 PM, Pascal Schumacher <[email protected] > wrote: > Hello, > > what is our policy regarding source incompatible changes to our APIs? > > Context: This commons io pull request: https://github.com/apache/comm > ons-io/pull/54/files propose removing unnecessary throws declarations > from public method signatures. > > Thanks, > > Pascal > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
