> Why not fix in 1.0.2?
That’s a good question. No single reason stounds out, but a handful of smaller
ones:
I'm lazy
Still a git newbie
1.0.2 has already had multiple release candidate/beta releases
This bug is two years old and been around forever and doesn't seem high
priority
I want more people testing the monolith branch
Want to social the "fixed in next release" concept
If folks don't find it compelling -- or, rather, someone says backport the
three-line fix, I'll do it :)
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: [email protected] Twitter: RichSalz
