I hope that identifying and fixing the issue doesn't take weeks but days. I don't think it's worth the trouble releasing two versions so quickly after another. Since 1.0.2 is only a patch I'd suggest to wait.
On 28.11.2010, at 20:52, Dirkjan Ochtman wrote: > On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt <[email protected]> wrote: >> Should we hold 1.0.2 for this? > > If releases are a whole bunch of work, then yes. > > However, since this doesn't seem to be a (recent) regression, it would > IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this > thing is fixed. > > Cheers, > > Dirkjan
