Hi Flinksters, I'd like to address an issue that has been concerning me for a while. In the Flink community we like to push "hotfixes" to the master. Hotfixes come in various shapes: From very small cosmetic changes (JavaDoc) to major refactoring and even new features.
IMHO we should move away from these hotfixes. Here's why: 1) They tend to break the master because they lack test coverage 2) They are usually not communicated with the maintainer or person working on the part being fixed 3) They are not properly documented for future reference or follow-ups (JIRA/Github) That's why I have chosen not to push hotfixes anymore. Even for small fixes, I'll open a JIRA/Github issue. The only exception might be fixing a comment. It improves communication, documentation, and test coverage. All this helps to mature Flink and develop the community in a transparent way. I'm not sure what our contribution guidelines say about this but I would like to update them to explicitly address hotfixes. Let me know what you think. Best, Max
