On 27 Jan 2014, at 09:17, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
It's really not a big deal if it's compilation errors and we
just have
to reorganize the imports: we clearly see the errors when we upgrade
so we can fix them easily. You just put it prominently in the release
notes and it's OK.
My thinking exactly.
Most of our problems when we upgrade don't come from API changes
but
from deeply hidden regressions. It's where we spend a lot of time
(yeah I have one to diagnose today on a 4.3 -> 4.4 upgrade :)).
+1
Thinking back to my time as pure Search user or user of any library,
handing the move of classes was never a big issue. Maybe a bit annoying, but basically
a no brainer. It becomes tricky if the actual API or behaviour changes.
—Hardy