On Mar 12, 2014, at 8:29 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
> On 12.03.2014 11:37, Jim Jagielski wrote: >> At the very least, upgrading from 2.4.7 to 2.4.8 should not >> cause this much pain. I will let the vote run a bit more to >> gauge additional feedback, but my sense says that 2.4.8 >> will likely be revoked/dropped and 2.4.9 will be proposed >> which either (1) removes r1573360 or (2) fixes this bug. > > Agreed, if it were only about 1.0.1e vs. 1.0.1f it would be not that big > an issue but since all Major versions seem to show the behavior and > there's no easy workaround for 0.9.8 except upgrading to 1.x, I'd say we > should implement the workaround suggested by Steve. > We'll need to put that into trunk, check that it works w/o causing a regression, first. My personal opinion is to pull out the commit in 2.4.x to give it more time in trunk to ferment and to release 2.4.9 w/o r1573360.
