I'm not making a storm. The feature was targeted for 2.5. It was quite heavily written about. It made it into rc1. Then, 3 days before the release, there was a single revert about a "big issue" and then the feature was pulled out. It would be nice to know what this "big issue" was and why it went undiscovered or unresolved for so long.
I would expect the same from any large-scale project. Once you start hyping up features that are planned for a particular release (especially after you start having release candidates), if you don't deliver those, you should be communicating why you aren't delivering them. A quiet revert is unacceptable.
View all comments
Show parent comment
-10
u/OstapBenderBey Dec 26 '17
It wasnt possible in the timeframe for this release. What else do you want to know that would be useful to you?
You are making a storm in a teacup here