kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Do we know if this is a KiCad source bug issue or a macos packaging
issue?  I was getting the distinct impression that it was the latter.  I
agree that we do not want to release 5.1.5 without a functioning macos
package.  I'm willing to hold off on the rc1 tag until we resolve this
issue.  It may give us an opportunity to fix some additional bug for 5.1.5.

On 10/20/19 9:02 PM, Adam Wolf wrote:
> Hi folks.
> 
> I was under the impression that although the macOS 10.15 betas had
> weird issues with KiCad, that the release Catalina was fine.  This may
> not be the case.  I am mobile today and only using my phone, so it's
> difficult for me to dig into it right now. If folks are still
> reporting that they create new projects, I would request that we
> postpone a release until this is resolved.
> 
> (I had posted a small and unhelpful error message, and was going to
> get a debugger on a 10.15 machine to get a real stack trace, but
> postponed going to 10.15 on that machine based on reports that it was
> working--but I may have to get that set up this week, unless someone
> else can.)
> 
> Adam
> 
> On Sun, Oct 20, 2019 at 6:50 PM Seth Hillbrand <seth@xxxxxxxxxxxxx> wrote:
>>
>> Hi Wayne-
>>
>> These should be fixed.  I've pushed the reload issue off to v6 as the
>> setting isn't available in the current file format as Ian mentioned, so
>> I've reset the associated bug with a new milestone.
>>
>> We should be clear for these reports now.  It's safe to tag 5.1.5RC1
>> from my perspective and we'll get some testing of the fixes.  It might
>> be good to get a 5.1.6 milestone in launchpad at the same time and I
>> will move all unaddressed items to that milestone so that we are only
>> fixing issues with 5.1.5 commits during the RC phase.
>>
>> Thoughts?
>>
>> -Seth
>>
>> On 2019-10-20 07:38, Wayne Stambaugh wrote:
>>> Thanks Seth,
>>>
>>> There is also this[1] bug and this[2] bug and this[3] bug related to
>>> the
>>> zone constraint changes.  I probably wont hold up the 5.1.5 release for
>>> them but they are behavioral changes which users will not expect.  The
>>> most annoying one is lp:1846028.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> [1]: https://bugs.launchpad.net/kicad/+bug/1842195
>>> [2]: https://bugs.launchpad.net/kicad/+bug/1846028
>>> [3]: https://bugs.launchpad.net/kicad/+bug/1846029
>>>
>>> On 10/20/19 10:13 AM, Seth Hillbrand wrote:
>>>> On 2019-10-20 06:41, Wayne Stambaugh wrote:
>>>>> Where are we on the 5.1.5 release?  I took a look at the bug tacker
>>>>> and
>>>>> the only serious bug I saw was the glib assertion bug[1].  How close
>>>>> are
>>>>> we to getting this fixed?  There is still some unexpected behavior
>>>>> with
>>>>> the constrained zone drawing and editing changes that should be fixed
>>>>> before we release.  I would like to tag -rc1 and start the string
>>>>> freeze
>>>>> by the end of October.
>>>>
>>>> Odd, I didn't see that one come through.  I'll fix that this weekend.
>>>>
>>>> -S
>>>>
>>>> Seth Hillbrand
>>>> KiCad Services Corporation
>>>> https://www.kipro-pcb.com
>>>> +1 530 302 5483 | +1 212 603 9372
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>> Seth Hillbrand
>> KiCad Services Corporation
>> https://www.kipro-pcb.com
>> +1 530 302 5483 | +1 212 603 9372
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp