Release 4.1.0

[jonorossi]

Pending Castle Core release (castleproject/Core#306) to bump minimum Castle Core version to end assembly version problems.

Knowing that we are bumping the minimum Castle Core version and that there are quite a few fixes in this release we should probably jump to 4.1.0.

I understand what people want from SemVer but it really is an illusion, to say that the public API/ABI hasn't changed doesn't mean you won't break a consumer, any behaviour change whether defective or not has the chance to impact someone relying on that behaviour. With that said I'll usually follow major.minor.patch with the level of impact concept in mind but not really follow SemVer.

Happy to hear your opinion whether you agree/disagree.

/cc @fir3pho3nixx

[ghost]

@jonorossi - I find semver easy to understand, I honestly dont mind. As long as we are releasing often it does not matter too much :)

[jnm2]

I thought semver had a provision for non-API (behavioral) breaking changes, but the version doesn't matter to me as long as the changes in behavior are called out.

Speaking of which, do you think anyone would be broken by my change?

[jonorossi]

Done.

• https://github.com/castleproject/Windsor/releases/tag/v4.1.0
• https://twitter.com/castleproject/status/913377642425966593