On Thu, Mar 26, 2015 at 10:19 AM, Richard Biener
wrote:
> On Thu, Mar 26, 2015 at 10:15 AM, Andreas Schwab wrote:
>> Jakub Jelinek writes:
>>
>>> Though, 5.0 milestone isn't completely meaningless, it means plan to fix it
>>> already before the release.
>>
>> That's true for all 5.1 milestone bu
On Thu, Mar 26, 2015 at 10:15 AM, Andreas Schwab wrote:
> Jakub Jelinek writes:
>
>> Though, 5.0 milestone isn't completely meaningless, it means plan to fix it
>> already before the release.
>
> That's true for all 5.1 milestone bugs as well. :-)
It would be "fix during development aka stage1-3
Jakub Jelinek writes:
> Though, 5.0 milestone isn't completely meaningless, it means plan to fix it
> already before the release.
That's true for all 5.1 milestone bugs as well. :-)
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4
Hi,
On 03/26/2015 09:52 AM, Jakub Jelinek wrote:
On Thu, Mar 26, 2015 at 09:36:30AM +0100, Richard Biener wrote:
On Thu, Mar 26, 2015 at 1:10 AM, Paolo Carlini wrote:
sorry if I missed part of the discussion about the new numbering scheme and
the answer to my question is already clear from th
On Thu, Mar 26, 2015 at 09:36:30AM +0100, Richard Biener wrote:
> On Thu, Mar 26, 2015 at 1:10 AM, Paolo Carlini
> wrote:
> > sorry if I missed part of the discussion about the new numbering scheme and
> > the answer to my question is already clear from that: why we do have 5.0 as
> > Milestone i
On Thu, Mar 26, 2015 at 1:10 AM, Paolo Carlini wrote:
> Hi,
>
> sorry if I missed part of the discussion about the new numbering scheme and
> the answer to my question is already clear from that: why we do have 5.0 as
> Milestone in Bugzilla instead of 5.1?!?
Yeah, well ... details. We chose to
Hi,
sorry if I missed part of the discussion about the new numbering scheme
and the answer to my question is already clear from that: why we do have
5.0 as Milestone in Bugzilla instead of 5.1?!?
Thanks,
Paolo.
