there's been some progress on the amd issue, ulrich spend some quality
detective time remote debugging :) so i guess there's a chance to have
that resolved.
j.
On Fri, Nov 30, 2012 at 12:51 PM, jeremy rosen
wrote:
> I think the main thing we are missing for 1.1.1 is the freeze with AMD
>
> and t
I think the main thing we are missing for 1.1.1 is the freeze with AMD
and the main fix we have is the MacOs crash (IIRC, feel free to correct me)
so if the AMD freeze is fixed it might be worth releasing even earlier
than that, and if doesn't get fixed, not later than that so mac user
can have t
i will try to finish (or almost finish...) my translation till that time :)
On 30 November 2012 09:13, johannes hanika wrote:
> On Fri, Nov 30, 2012 at 12:06 PM, Togan Muftuoglu
> wrote:
> > On 11/29/2012 11:04 PM, James C. McPherson wrote:
> >> On 30/11/12 07:46 AM, Pascal de Bruijn wrote:
> >
On Fri, Nov 30, 2012 at 12:06 PM, Togan Muftuoglu
wrote:
> On 11/29/2012 11:04 PM, James C. McPherson wrote:
>> On 30/11/12 07:46 AM, Pascal de Bruijn wrote:
>>> Hi,
>>>
>>> It seems we've had a pretty good release with 1.1.0, still in the
>>> meanwhile some bugs have already gotten fixed. I would
On 11/29/2012 11:04 PM, James C. McPherson wrote:
> On 30/11/12 07:46 AM, Pascal de Bruijn wrote:
>> Hi,
>>
>> It seems we've had a pretty good release with 1.1.0, still in the
>> meanwhile some bugs have already gotten fixed. I would prefer to
>> release 1.1.1 fairly quickly, no point is keeping t
Am Donnerstag, 29. November 2012, 22:46:41 schrub Pascal de Bruijn:
> Hi,
Hi.
[...]
> So I'm hoping we can do a 1.1.1 release during the weekend of 14-15 Dec
> 2012.
Sounds good.
> Considering the fairly short cycle, I'd prefer if strings won't get broken.
Too late. It's only key accel descri
On 30/11/12 07:46 AM, Pascal de Bruijn wrote:
> Hi,
>
> It seems we've had a pretty good release with 1.1.0, still in the
> meanwhile some bugs have already gotten fixed. I would prefer to
> release 1.1.1 fairly quickly, no point is keeping these fixes back.
>
> So while nothing is set in stone yet
Hi,
It seems we've had a pretty good release with 1.1.0, still in the
meanwhile some bugs have already gotten fixed. I would prefer to
release 1.1.1 fairly quickly, no point is keeping these fixes back.
So while nothing is set in stone yet, I want to target a 1.1.1 release
before christmas. But r
And thanks to boucman, I've just corrected 1 more bug and add an easy
feature.
The Pull request should have been automatically updated.
Just a question here : is this PR with about 5 commits clean enough to
be reviewed, or should I create a new branch, rebase and do another PR ?
Thanks,
Aldric
