commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita" <>
Subject [IMAGING] Add another backward incompatible change pre alpha2
Date Wed, 26 Jun 2019 19:31:13 GMT
Hi all,
We have added one binary backward incompatible change since commons-imaging-1.0-alpha1. Which
means commons-imaging-alpha2 will be both behavior and binary incompatible.
There was some discussion around alpha/beta releases rencetly-ish [1]
I am writing to confirm that we can add more BC incompatible changes. I believe there were
some comments about having a per-component policy for what alpha & beta means, but we
don't have a general consensus or policy.
So I prefer to check now, rather than have a release blocked, or have to revert changes.
The breaking change would be in a pull request contributed by a user:
The contributor wrote an excellent pull request, and held back on breaking compatibility.
But since we are already breaking BC, we could very well complete the PR and this way we would
be closer to being compliant with the standard.




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message