Alex, by continuing to block Justin, you're making this exactly the kind of grind that you've said we should avoid. If you just said "okay cool, make the change!" that's painless and won't discourage any potential release managers.
- Josh On May 23, 2017 9:52 PM, "Alex Harui" <aha...@adobe.com.invalid> wrote: On 5/23/17, 1:03 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi Alex, > >I disagree … if things like this are found, why do them later instead of >just fixing things and not have to deal with them again? Because we want to demonstrate that releasing is simple and fun, not some grind through stuff that doesn't matter. If we clean this up now, we will again prove that this community cannot focus on important things. The casual observer will take a look at what we talk about and wonder why we are not addressing the top 9 takeaways from ApacheCon. Is this really more important than fixing some NPE or transpiler issue that will affect many of our customers? Usually, late in a release cycle, the only changes should be stop-ship. IMO, best time to clean this up is right after the release when we flood commits@ with merging the release branch back to develop and master. Then 220 header changes will not make significant noise. My 2 cents, -Alex
