[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2 release blocking bugs left for 25.1!
From: |
Eli Zaretskii |
Subject: |
Re: 2 release blocking bugs left for 25.1! |
Date: |
Tue, 21 Jun 2016 21:51:21 +0300 |
> From: John Wiegley <address@hidden>
> Date: Tue, 21 Jun 2016 11:43:49 -0700
> Cc: address@hidden
>
> > And it's a regression in 25.1 due to the new undo code.
>
> This does sounds like a blocker, then. What are the repercussions for fixing
> the issue? Will it need a full round of pretesting to become ready for the
> release candidate?
No, I don't think so. It's a localized solution for a localized
problem.
- 2 release blocking bugs left for 25.1!, John Wiegley, 2016/06/18
- Re: 2 release blocking bugs left for 25.1!, Eli Zaretskii, 2016/06/18
- Re: 2 release blocking bugs left for 25.1!, Phillip Lord, 2016/06/20
- Re: 2 release blocking bugs left for 25.1!, John Wiegley, 2016/06/20
- Re: 2 release blocking bugs left for 25.1!, Phillip Lord, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!, Stefan Monnier, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!, John Wiegley, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!,
Eli Zaretskii <=
- Re: 2 release blocking bugs left for 25.1!, John Wiegley, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!, Phillip Lord, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!, Óscar Fuentes, 2016/06/21
- Re: 2 release blocking bugs left for 25.1!, Phillip Lord, 2016/06/22
Re: 2 release blocking bugs left for 25.1!, Paul Eggert, 2016/06/21