Blog post about backward compatibility (#22)
Blog post about backward compatibility (#22)

* Blog post about backward compatibility

* Update 2017-07-20-backward-compatibility.md

I've made some edits, and have a few questions:
- Can we say "flag" rather than "option". Not a big deal, but I like using just one word when possible.
- When the flag is removed and so you can no longer disable the behaviour - are we announcing this in release notes?
- True that you can disable the behaviour while the flag is still present? I added this to the text.
- Will these changes be across Bazel, or only for extensions/skylark?
- "If the build is successful, you can safely update to the new version." Should we be a broader here? What if the change breaks a test behaviour? Maybe we should say "If your tests with the new change are successful, you can update to the new version." as each change may need different tests (though in many cases I'm sure it's just verifying that it builds)

* Update 2017-07-20-backward-compatibility.md

* Update 2017-07-20-backward-compatibility.md

davidzchen/bazel-blog,davidzchen/bazel-blog,laszlocsomor/bazel-blog,bazelbuild/bazel-blog,laszlocsomor/bazel-blog,laszlocsomor/bazel-blog,bazelbuild/bazel-blog,davidzchen/bazel-blog,bazelbuild/bazel-blog,laszlocsomor/bazel-blog,davidzchen/bazel-blog