Comment 14 for bug 186869

Sorry Murray, haven't had much time lately to look into this. I'm asking the Technical Board for clarification on microreleases.

What would be the lowest version of glom that would fix this bug? From Loïc Minier's investigation above going from 1.6.0 to 1.6.6 seems to introduce and awful lot beyond just fixing this bug. It's a slippery slope here as I'm sure there are always improvements with every release, but the more updated code we introduce the more potential for regressions and unintentional side-effects. Hopefully we can get this resolved soon, I don't like seeing bug fixes just lying around.