On Mon, Jul 15, 2013 at 11:02:09PM +0000, "Jóhann B. Guðmundsson" wrote:
I would assume they take into account hard valid technical arguments not change in workflow ( which any change might bring ) or people pluses or minuses but maybe that's just my wishful thinking.
"This has a change in workflow" _is_ hard, valid technical argument. Any change needs to overcome that in one of two ways: 1) minimize the pain of transition with compatibility paths, documentation, and serious thought about the user experience for current users; and 2) bring significant new value that weighs against it. The best changes work on both sides of the equation, of course.