On 12 June 2016 at 12:43, Benedikt Ritter <brit...@apache.org> wrote:
> sebb <seb...@gmail.com> schrieb am So., 12. Juni 2016 um 13:38 Uhr:
>
>> On 12 June 2016 at 12:00, Benedikt Ritter <brit...@apache.org> wrote:
>> > Hi,
>> >
>> > I've uploaded the verbose Clirr report to my space at home.apache.org
>> [1].
>> > Do we have to fix all of this in order to release 6.0?
>>
>> No, most of the changes don't break strict BC.
>>
>> The main changes to the interfaces don't break BC and are highly
>> unlikely to affect source because there are abstract implementation
>> classes.
>>
>> See the changes.xml file and release notes for some details.
>>
>
> Thank you, I will have a look. Can we compile a list of things we need to
> fix for 6.0?

Unfortunately the lack of updates has caused downstream users to rely
on non-released code.
I think we should try and ensure that we don't make things worse.

Therefore I don't think we can compile a full list without assistance
from FindBugs and other consumers of the code.

I suspect this will be an iterative process to try and find the best
compromise that suits these users as well as users who have only used
formal releases.

> Benedikt
>
>
>>
>> > Benedikt
>> >
>> > [1]
>> >
>> http://home.apache.org/~britter/commons/bcel/6.0-SNAPSHOT/clirr-report.html
>> >
>> > sebb <seb...@gmail.com> schrieb am Mi., 8. Juni 2016 um 11:54 Uhr:
>> >
>> >> On 8 June 2016 at 10:46, Benedikt Ritter <brit...@apache.org> wrote:
>> >> > Hello sebb,
>> >> >
>> >> > sebb <seb...@gmail.com> schrieb am Mi., 8. Juni 2016 um 11:21 Uhr:
>> >> >
>> >> >> Was that the full report, or the 'quietened' one?
>> >> >> There's a Clirr suppression file which removes some diffs that are
>> >> >> considered non-breaking (as per the changes description)
>> >> >> (otherwise the report is rather difficult to read)
>> >> >>
>> >> >> To show all the errors, use -P!quieten-clirr or
>> -Dclirr.allDifferences
>> >> >>
>> >> >
>> >> > The report is the result of running mvn clean site. So if
>> quiten-clirr is
>> >> > activated by default it's the 'quitened' one (sorry I currently don't
>> >> have
>> >> > time to look into the pom).
>> >>
>> >> Yes, it is the default.
>> >>
>> >> > I can upload the "real" report to home.apache.org tonight when I'm at
>> >> home.
>> >>
>> >> OK, thanks.
>> >>
>> >> > Benedikt
>> >> >
>> >> >
>> >> >>
>> >> >> On 8 June 2016 at 09:35, Benedikt Ritter <brit...@apache.org> wrote:
>> >> >> > Hi all,
>> >> >> >
>> >> >> > I've published the BCEL website after reverting the package rename.
>> >> Here
>> >> >> > [1] is the Clirr report of the current code base.
>> >> >> >
>> >> >> > Benedikt
>> >> >> >
>> >> >> > [1]
>> http://commons.apache.org/proper/commons-bcel/clirr-report.html
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> >> For additional commands, e-mail: dev-h...@commons.apache.org
>> >> >>
>> >> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> For additional commands, e-mail: dev-h...@commons.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to