It's assumed that 1.2.0 will ship with bugs (because it's software). Can you clarify the conditions under which this bug occurs? I'm inclined to agree with Filipe that it's release blocking, but if it the conditions to induce are very rare, I might change my mind. Given that you induced it without apparent effort, I don't think it's likely to be rare.
B. On 28 March 2012 19:06, Stefan Kögl <[email protected]> wrote: > On 03/28/2012 07:59 PM, Jan Lehnardt wrote: >> Hi Stefan, thanks for bringing this up. This is just to explain the >> procedure. >> A vote happens on a fixed package and no changes to the package can be made >> during the vote. If we find a flaw significant enough to include a fix into >> the release that is currently being voted on, we can abort the vote, fix, >> re-package and start a new vote, like we've done before. > > Thanks for the explanation, that's exactly what I expected ;) What I > meant was, that we should either > > * rule out that this affects 1.2.x (but apparently it does) > * fix it and start another round of votes > > Anyway, I wanted to be in time before somebody closes the vote and 1.2 > might be shipped with a bug. > > > -- Stefan
