Re:Why Learning Angular 2 Was Excruciating
by olavgg on Monday September 19, 2016 @05:21PM
(#12534842)
No no and no. Breaking changes are not ok, not even slightly!
It's not acceptable after an alpha release, It's especially not acceptable after a beta release. And it is offensive against developers to have breaking changes from the first release candidate and onwards.
Even for major releases, breaking changes is a VERY BAD thing. But sometimes it is unfortunately unavoidable.
Re:Why Learning Angular 2 Was Excruciating
by ajmurmann on Monday September 19, 2016 @05:24PM
(#12534872)
It's ok if the first RC had breaking changes but after that you should have only bug fixes between RC versions. It seems unusual that some breaking feature got for some reason left out from an earlier build that was considered a potential candidate for release.
A release candidate isn't a release, and the release may have breaking changes from the RC, and obviously an RC of anything that would be a semver major release may have breaking changes from the previous actual release. So, in either direction, an RC may have breaking changes.
Ideally, the last RC should not have breaking changes between it and the actual release, but we wouldn't need a "candidate" if we knew things would be ideal.