Re: [Kicad-developers] 5.0.1 release status.

[eldar.khayrullin]

Hello. I found the next bug #1798124
 Исходное сообщение От: Wayne Stambaugh  
Дата: 16.10.18  16:49  (GMT+03:00) Кому: kicad-developers@lists.launchpad.net 
Тема: Re: [Kicad-developers] 5.0.1 release status. 
Hi Jean-Samuel,

It looks like you will have cherry pick commit 9a3cfb857 from the
development branch to build on any version of Ubuntu that uses boost
prior to version 1.59.  I've attached a copy of the patch so you do not
have to cherry pick it yourself.  I think I was the responsible for
merging John's patch and forgot to merge it into the 5.0 branch (which I
just did for 5.0.2).  I apologize for the inconvenience.  Maybe we
should start doing -rc1 releases of the next stable release to iron out
any of these issues before the final release.

Cheers,

Wayne

On 10/16/2018 9:02 AM, Jean-Samuel Reynaud wrote:
> Hi Wayne,
> 
> Yes the bug #1785377 affect also this release. Did I need to plan a
> workarround to allow this build ?
> 
> Regards,
> Le 15/10/2018 à 23:37, John Beard a écrit :
>> Hi Wayne,
>>
>> There was a commit on master made for this purpose: 9a3cfb857. The
>> function is to remove a failing test and thereby avoid having to
>> exclude it from the CTest harness, which doesn't work on old Boosts. I
>> thought it was in v5, but it is evidently not (and git branch
>> --contains concurs).
>>
>> A simple cherry-pick should work.
>>
>> Cheers,
>>
>> John
>> On Mon, Oct 15, 2018 at 7:03 PM Wayne Stambaugh  wrote:
>>>
>>> JS is on the mailing list.  I suspect he will reply soon.
>>>
>>> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
>>>> Hi all!
>>>>
>>>> I've been awaiting the 5.0.1 release to be officially available via the
>>>> ppa of js-reynaud. Though unfortunatley there's an issue with the
>>>> build: 
>>>> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
>>>> Actually it's the tests that cause the
>>>> issue: 
>>>> https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
>>>> at the very bottom
>>>>
>>>> I'm not yet in the position to tell the cause, but I would like raise
>>>> awareness of this. Does Js-Reynaud read this here?, shall I contact him
>>>> directly via launchpad, ? What best to do?
>>>>
>>>> Cheers
>>>> Ronnie
>>>>
>>>>
>>>> Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
>>>> mailto:stambau...@gmail.com>>:
>>>>
>>>> We will have to do the usual tagging of all of the repos with 5.0.2
>>>> so I
>>>> will have to wait to see if there any issues.  I shouldn't take very
>>>> long so 5.0.1 may be a very short lived release.
>>>>
>>>> On 10/14/2018 01:13 PM, Adam Wolf wrote:
>>>> > I think there are some 5.0.1s already up for download... Any issue
>>>> just
>>>> > going to 5.0.2?
>>>> >
>>>> > Adam
>>>> >
>>>> > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
>>>> mailto:stambau...@gmail.com>
>>>> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> wrote:
>>>> >
>>>> > I'm fine with pushing the release back another week.  I would
>>>> rather not
>>>> > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
>>>> > breaking Eagle import is not good.  I see one of two options 
>>>>here.
>>>> > Retag 5.0.1 with the current changes or release 5.0.2
>>>> immediately.  I
>>>> > don't know which is more work for our packagers so I am open
>>>> to either
>>>> > option.  Please let me know what works best for you and I will
>>>> go with
>>>> > that option.
>>>> >
>>>> > Cheers,
>>>> >
>>>> > Wayne
>>>> >
>>>> > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
>>>> >  > Hi Wayne, et al-
>>>> >  >
>>>> >  > There is a critical bug that I introduced
>>>> >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
>>>> It a

Re: [Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

Hi Jean-Samuel,

It looks like you will have cherry pick commit 9a3cfb857 from the
development branch to build on any version of Ubuntu that uses boost
prior to version 1.59.  I've attached a copy of the patch so you do not
have to cherry pick it yourself.  I think I was the responsible for
merging John's patch and forgot to merge it into the 5.0 branch (which I
just did for 5.0.2).  I apologize for the inconvenience.  Maybe we
should start doing -rc1 releases of the next stable release to iron out
any of these issues before the final release.

Cheers,

Wayne

On 10/16/2018 9:02 AM, Jean-Samuel Reynaud wrote:
> Hi Wayne,
> 
> Yes the bug #1785377 affect also this release. Did I need to plan a
> workarround to allow this build ?
> 
> Regards,
> Le 15/10/2018 à 23:37, John Beard a écrit :
>> Hi Wayne,
>>
>> There was a commit on master made for this purpose: 9a3cfb857. The
>> function is to remove a failing test and thereby avoid having to
>> exclude it from the CTest harness, which doesn't work on old Boosts. I
>> thought it was in v5, but it is evidently not (and git branch
>> --contains concurs).
>>
>> A simple cherry-pick should work.
>>
>> Cheers,
>>
>> John
>> On Mon, Oct 15, 2018 at 7:03 PM Wayne Stambaugh  wrote:
>>>
>>> JS is on the mailing list.  I suspect he will reply soon.
>>>
>>> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
 Hi all!

 I've been awaiting the 5.0.1 release to be officially available via the
 ppa of js-reynaud. Though unfortunatley there's an issue with the
 build: 
 https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
 Actually it's the tests that cause the
 issue: 
 https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
 at the very bottom

 I'm not yet in the position to tell the cause, but I would like raise
 awareness of this. Does Js-Reynaud read this here?, shall I contact him
 directly via launchpad, ? What best to do?

 Cheers
 Ronnie


 Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
 mailto:stambau...@gmail.com>>:

 We will have to do the usual tagging of all of the repos with 5.0.2
 so I
 will have to wait to see if there any issues.  I shouldn't take very
 long so 5.0.1 may be a very short lived release.

 On 10/14/2018 01:13 PM, Adam Wolf wrote:
 > I think there are some 5.0.1s already up for download... Any issue
 just
 > going to 5.0.2?
 >
 > Adam
 >
 > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
 mailto:stambau...@gmail.com>
 > >> wrote:
 >
 > I'm fine with pushing the release back another week.  I would
 rather not
 > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
 > breaking Eagle import is not good.  I see one of two options 
 here.
 > Retag 5.0.1 with the current changes or release 5.0.2
 immediately.  I
 > don't know which is more work for our packagers so I am open
 to either
 > option.  Please let me know what works best for you and I will
 go with
 > that option.
 >
 > Cheers,
 >
 > Wayne
 >
 > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
 >  > Hi Wayne, et al-
 >  >
 >  > There is a critical bug that I introduced
 >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
 It affects
 >  > certain Eagle files imports and causes a crash.
 >  >
 >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
 problems.
 >  >
 >  > Between this and the footprint wizard, we may wish to
 announce a
 > 5.0.2
 >  > sooner rather than later.  Or packagers may wish to pull in 
 the
 >  > post-5.0.2 tagged commits as patches to their builds before
 > announcement.
 >  >
 >  > -S
 >  >
 >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
 >  > mailto:stambau...@gmail.com>
 >
 > 
   >
 >  > Does anyone need more time to get packages built for the
 > 5.0.1 release?
 >  > I am hoping to release on Sunday if possible.  Please
 let me
 > know if you
 >  > need any additional time.
 >  >
 >  > Cheers,
 > 

Re: [Kicad-developers] 5.0.1 release status.

[Jean-Samuel Reynaud]

Hi Wayne,

Yes the bug #1785377 affect also this release. Did I need to plan a
workarround to allow this build ?

Regards,
Le 15/10/2018 à 23:37, John Beard a écrit :
> Hi Wayne,
> 
> There was a commit on master made for this purpose: 9a3cfb857. The
> function is to remove a failing test and thereby avoid having to
> exclude it from the CTest harness, which doesn't work on old Boosts. I
> thought it was in v5, but it is evidently not (and git branch
> --contains concurs).
> 
> A simple cherry-pick should work.
> 
> Cheers,
> 
> John
> On Mon, Oct 15, 2018 at 7:03 PM Wayne Stambaugh  wrote:
>>
>> JS is on the mailing list.  I suspect he will reply soon.
>>
>> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
>>> Hi all!
>>>
>>> I've been awaiting the 5.0.1 release to be officially available via the
>>> ppa of js-reynaud. Though unfortunatley there's an issue with the
>>> build: 
>>> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
>>> Actually it's the tests that cause the
>>> issue: 
>>> https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
>>> at the very bottom
>>>
>>> I'm not yet in the position to tell the cause, but I would like raise
>>> awareness of this. Does Js-Reynaud read this here?, shall I contact him
>>> directly via launchpad, ? What best to do?
>>>
>>> Cheers
>>> Ronnie
>>>
>>>
>>> Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
>>> mailto:stambau...@gmail.com>>:
>>>
>>> We will have to do the usual tagging of all of the repos with 5.0.2
>>> so I
>>> will have to wait to see if there any issues.  I shouldn't take very
>>> long so 5.0.1 may be a very short lived release.
>>>
>>> On 10/14/2018 01:13 PM, Adam Wolf wrote:
>>> > I think there are some 5.0.1s already up for download... Any issue
>>> just
>>> > going to 5.0.2?
>>> >
>>> > Adam
>>> >
>>> > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
>>> mailto:stambau...@gmail.com>
>>> > >> wrote:
>>> >
>>> > I'm fine with pushing the release back another week.  I would
>>> rather not
>>> > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
>>> > breaking Eagle import is not good.  I see one of two options here.
>>> > Retag 5.0.1 with the current changes or release 5.0.2
>>> immediately.  I
>>> > don't know which is more work for our packagers so I am open
>>> to either
>>> > option.  Please let me know what works best for you and I will
>>> go with
>>> > that option.
>>> >
>>> > Cheers,
>>> >
>>> > Wayne
>>> >
>>> > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
>>> >  > Hi Wayne, et al-
>>> >  >
>>> >  > There is a critical bug that I introduced
>>> >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
>>> It affects
>>> >  > certain Eagle files imports and causes a crash.
>>> >  >
>>> >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
>>> problems.
>>> >  >
>>> >  > Between this and the footprint wizard, we may wish to
>>> announce a
>>> > 5.0.2
>>> >  > sooner rather than later.  Or packagers may wish to pull in the
>>> >  > post-5.0.2 tagged commits as patches to their builds before
>>> > announcement.
>>> >  >
>>> >  > -S
>>> >  >
>>> >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
>>> >  > mailto:stambau...@gmail.com>
>>> >
>>> > 
>>> >> >  >
>>> >  > Does anyone need more time to get packages built for the
>>> > 5.0.1 release?
>>> >  > I am hoping to release on Sunday if possible.  Please
>>> let me
>>> > know if you
>>> >  > need any additional time.
>>> >  >
>>> >  > Cheers,
>>> >  >
>>> >  > Wayne
>>> >  >
>>> >  > ___
>>> >  > Mailing list: https://launchpad.net/~kicad-developers
>>> > 
>>> >  > 
>>> >  > Post to : kicad-developers@lists.launchpad.net
>>> 
>>> > >> >
>>> >  > >> 
>>> > >> <

Re: [Kicad-developers] 5.0.1 release status.

[John Beard]

Hi Wayne,

There was a commit on master made for this purpose: 9a3cfb857. The
function is to remove a failing test and thereby avoid having to
exclude it from the CTest harness, which doesn't work on old Boosts. I
thought it was in v5, but it is evidently not (and git branch
--contains concurs).

A simple cherry-pick should work.

Cheers,

John
On Mon, Oct 15, 2018 at 7:03 PM Wayne Stambaugh  wrote:
>
> JS is on the mailing list.  I suspect he will reply soon.
>
> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
> > Hi all!
> >
> > I've been awaiting the 5.0.1 release to be officially available via the
> > ppa of js-reynaud. Though unfortunatley there's an issue with the
> > build: 
> > https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
> > Actually it's the tests that cause the
> > issue: 
> > https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
> > at the very bottom
> >
> > I'm not yet in the position to tell the cause, but I would like raise
> > awareness of this. Does Js-Reynaud read this here?, shall I contact him
> > directly via launchpad, ? What best to do?
> >
> > Cheers
> > Ronnie
> >
> >
> > Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
> > mailto:stambau...@gmail.com>>:
> >
> > We will have to do the usual tagging of all of the repos with 5.0.2
> > so I
> > will have to wait to see if there any issues.  I shouldn't take very
> > long so 5.0.1 may be a very short lived release.
> >
> > On 10/14/2018 01:13 PM, Adam Wolf wrote:
> > > I think there are some 5.0.1s already up for download... Any issue
> > just
> > > going to 5.0.2?
> > >
> > > Adam
> > >
> > > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > > >> wrote:
> > >
> > > I'm fine with pushing the release back another week.  I would
> > rather not
> > > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
> > > breaking Eagle import is not good.  I see one of two options here.
> > > Retag 5.0.1 with the current changes or release 5.0.2
> > immediately.  I
> > > don't know which is more work for our packagers so I am open
> > to either
> > > option.  Please let me know what works best for you and I will
> > go with
> > > that option.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> > >  > Hi Wayne, et al-
> > >  >
> > >  > There is a critical bug that I introduced
> > >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
> > It affects
> > >  > certain Eagle files imports and causes a crash.
> > >  >
> > >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
> > problems.
> > >  >
> > >  > Between this and the footprint wizard, we may wish to
> > announce a
> > > 5.0.2
> > >  > sooner rather than later.  Or packagers may wish to pull in the
> > >  > post-5.0.2 tagged commits as patches to their builds before
> > > announcement.
> > >  >
> > >  > -S
> > >  >
> > >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> > >  > mailto:stambau...@gmail.com>
> > >
> > > 
> >  > >  >
> > >  > Does anyone need more time to get packages built for the
> > > 5.0.1 release?
> > >  > I am hoping to release on Sunday if possible.  Please
> > let me
> > > know if you
> > >  > need any additional time.
> > >  >
> > >  > Cheers,
> > >  >
> > >  > Wayne
> > >  >
> > >  > ___
> > >  > Mailing list: https://launchpad.net/~kicad-developers
> > > 
> > >  > 
> > >  > Post to : kicad-developers@lists.launchpad.net
> > 
> > >  > >
> > >  >  > 
> > >  > >>
> > >  > Unsubscribe : https://launchpad.net/~kicad-developers
> > > 
> > >  >   

Re: [Kicad-developers] 5.0.1 release status.

[Ronnie Gaensli]

@JS: I figured that commit
https://git.launchpad.net/kicad/commit/?id=9a3cfb8 does the trick when
cherry picked on to the 5.0 branch... But that's all I can say.

Cheers
Ronnie


Am Mo., 15. Okt. 2018 um 20:03 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> JS is on the mailing list.  I suspect he will reply soon.
>
> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
> > Hi all!
> >
> > I've been awaiting the 5.0.1 release to be officially available via the
> > ppa of js-reynaud. Though unfortunatley there's an issue with the
> > build:
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
> > Actually it's the tests that cause the
> > issue:
> https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
> > at the very bottom
> >
> > I'm not yet in the position to tell the cause, but I would like raise
> > awareness of this. Does Js-Reynaud read this here?, shall I contact him
> > directly via launchpad, ? What best to do?
> >
> > Cheers
> > Ronnie
> >
> >
> > Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
> > mailto:stambau...@gmail.com>>:
> >
> > We will have to do the usual tagging of all of the repos with 5.0.2
> > so I
> > will have to wait to see if there any issues.  I shouldn't take very
> > long so 5.0.1 may be a very short lived release.
> >
> > On 10/14/2018 01:13 PM, Adam Wolf wrote:
> > > I think there are some 5.0.1s already up for download... Any issue
> > just
> > > going to 5.0.2?
> > >
> > > Adam
> > >
> > > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > > >>
> wrote:
> > >
> > > I'm fine with pushing the release back another week.  I would
> > rather not
> > > release 5.0.1 with this bug.  We have a lot of ex-Eagle users
> and
> > > breaking Eagle import is not good.  I see one of two options
> here.
> > > Retag 5.0.1 with the current changes or release 5.0.2
> > immediately.  I
> > > don't know which is more work for our packagers so I am open
> > to either
> > > option.  Please let me know what works best for you and I will
> > go with
> > > that option.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> > >  > Hi Wayne, et al-
> > >  >
> > >  > There is a critical bug that I introduced
> > >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
> > It affects
> > >  > certain Eagle files imports and causes a crash.
> > >  >
> > >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
> > problems.
> > >  >
> > >  > Between this and the footprint wizard, we may wish to
> > announce a
> > > 5.0.2
> > >  > sooner rather than later.  Or packagers may wish to pull in
> the
> > >  > post-5.0.2 tagged commits as patches to their builds before
> > > announcement.
> > >  >
> > >  > -S
> > >  >
> > >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> > >  > mailto:stambau...@gmail.com>
> > >
> > > 
> >  > >  >
> > >  > Does anyone need more time to get packages built for the
> > > 5.0.1 release?
> > >  > I am hoping to release on Sunday if possible.  Please
> > let me
> > > know if you
> > >  > need any additional time.
> > >  >
> > >  > Cheers,
> > >  >
> > >  > Wayne
> > >  >
> > >  > ___
> > >  > Mailing list: https://launchpad.net/~kicad-developers
> > > 
> > >  > 
> > >  > Post to : kicad-developers@lists.launchpad.net
> > 
> > >  > >
> > >  >  > 
> > >  > >>
> > >  > Unsubscribe : https://launchpad.net/~kicad-developers
> > > 
> > >  > 
> > >  > More help   : https://help.launchpad.net/ListHelp
> > >  >
> >  

Re: [Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

JS is on the mailing list.  I suspect he will reply soon.

On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
> Hi all!
> 
> I've been awaiting the 5.0.1 release to be officially available via the
> ppa of js-reynaud. Though unfortunatley there's an issue with the
> build: 
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
> Actually it's the tests that cause the
> issue: 
> https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
> at the very bottom 
> 
> I'm not yet in the position to tell the cause, but I would like raise
> awareness of this. Does Js-Reynaud read this here?, shall I contact him
> directly via launchpad, ? What best to do?
> 
> Cheers
> Ronnie
> 
> 
> Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
> mailto:stambau...@gmail.com>>:
> 
> We will have to do the usual tagging of all of the repos with 5.0.2
> so I
> will have to wait to see if there any issues.  I shouldn't take very
> long so 5.0.1 may be a very short lived release.
> 
> On 10/14/2018 01:13 PM, Adam Wolf wrote:
> > I think there are some 5.0.1s already up for download... Any issue
> just
> > going to 5.0.2?
> >
> > Adam
> >
> > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
> mailto:stambau...@gmail.com>
> > >> wrote:
> >
> >     I'm fine with pushing the release back another week.  I would
> rather not
> >     release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
> >     breaking Eagle import is not good.  I see one of two options here.
> >     Retag 5.0.1 with the current changes or release 5.0.2
> immediately.  I
> >     don't know which is more work for our packagers so I am open
> to either
> >     option.  Please let me know what works best for you and I will
> go with
> >     that option.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> >      > Hi Wayne, et al-
> >      >
> >      > There is a critical bug that I introduced
> >      > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1. 
> It affects
> >      > certain Eagle files imports and causes a crash.
> >      >
> >      > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
> problems.
> >      >
> >      > Between this and the footprint wizard, we may wish to
> announce a
> >     5.0.2
> >      > sooner rather than later.  Or packagers may wish to pull in the
> >      > post-5.0.2 tagged commits as patches to their builds before
> >     announcement.
> >      >
> >      > -S
> >      >
> >      > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> >      > mailto:stambau...@gmail.com>
> >
> >     
>  >      >
> >      >     Does anyone need more time to get packages built for the
> >     5.0.1 release?
> >      >     I am hoping to release on Sunday if possible.  Please
> let me
> >     know if you
> >      >     need any additional time.
> >      >
> >      >     Cheers,
> >      >
> >      >     Wayne
> >      >
> >      >     ___
> >      >     Mailing list: https://launchpad.net/~kicad-developers
> >     
> >      >     
> >      >     Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >      >      
> >      >>
> >      >     Unsubscribe : https://launchpad.net/~kicad-developers
> >     
> >      >     
> >      >     More help   : https://help.launchpad.net/ListHelp
> >      >
> >
> >     ___
> >     Mailing list: https://launchpad.net/~kicad-developers
> >     
> >     Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> 

Re: [Kicad-developers] 5.0.1 release status.

[Ronnie Gaensli]

Hi all!

I've been awaiting the 5.0.1 release to be officially available via the ppa
of js-reynaud. Though unfortunatley there's an issue with the build:
https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
Actually it's the tests that cause the issue:
https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
at the very bottom

I'm not yet in the position to tell the cause, but I would like raise
awareness of this. Does Js-Reynaud read this here?, shall I contact him
directly via launchpad, ? What best to do?

Cheers
Ronnie


Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> We will have to do the usual tagging of all of the repos with 5.0.2 so I
> will have to wait to see if there any issues.  I shouldn't take very
> long so 5.0.1 may be a very short lived release.
>
> On 10/14/2018 01:13 PM, Adam Wolf wrote:
> > I think there are some 5.0.1s already up for download... Any issue just
> > going to 5.0.2?
> >
> > Adam
> >
> > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh  > > wrote:
> >
> > I'm fine with pushing the release back another week.  I would rather
> not
> > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
> > breaking Eagle import is not good.  I see one of two options here.
> > Retag 5.0.1 with the current changes or release 5.0.2 immediately.  I
> > don't know which is more work for our packagers so I am open to
> either
> > option.  Please let me know what works best for you and I will go
> with
> > that option.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> >  > Hi Wayne, et al-
> >  >
> >  > There is a critical bug that I introduced
> >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.  It
> affects
> >  > certain Eagle files imports and causes a crash.
> >  >
> >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
> problems.
> >  >
> >  > Between this and the footprint wizard, we may wish to announce a
> > 5.0.2
> >  > sooner rather than later.  Or packagers may wish to pull in the
> >  > post-5.0.2 tagged commits as patches to their builds before
> > announcement.
> >  >
> >  > -S
> >  >
> >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> >  > mailto:stambau...@gmail.com>
> > >>:
> >  >
> >  > Does anyone need more time to get packages built for the
> > 5.0.1 release?
> >  > I am hoping to release on Sunday if possible.  Please let me
> > know if you
> >  > need any additional time.
> >  >
> >  > Cheers,
> >  >
> >  > Wayne
> >  >
> >  > ___
> >  > Mailing list: https://launchpad.net/~kicad-developers
> > 
> >  > 
> >  > Post to : kicad-developers@lists.launchpad.net
> > 
> >  >  > >
> >  > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> >  > 
> >  > More help   : https://help.launchpad.net/ListHelp
> >  >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

We will have to do the usual tagging of all of the repos with 5.0.2 so I 
will have to wait to see if there any issues.  I shouldn't take very 
long so 5.0.1 may be a very short lived release.


On 10/14/2018 01:13 PM, Adam Wolf wrote:
I think there are some 5.0.1s already up for download... Any issue just 
going to 5.0.2?


Adam

On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh > wrote:


I'm fine with pushing the release back another week.  I would rather not
release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
breaking Eagle import is not good.  I see one of two options here.
Retag 5.0.1 with the current changes or release 5.0.2 immediately.  I
don't know which is more work for our packagers so I am open to either
option.  Please let me know what works best for you and I will go with
that option.

Cheers,

Wayne

On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
 > Hi Wayne, et al-
 >
 > There is a critical bug that I introduced
 > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.  It affects
 > certain Eagle files imports and causes a crash.
 >
 > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra problems.
 >
 > Between this and the footprint wizard, we may wish to announce a
5.0.2
 > sooner rather than later.  Or packagers may wish to pull in the
 > post-5.0.2 tagged commits as patches to their builds before
announcement.
 >
 > -S
 >
 > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
 > mailto:stambau...@gmail.com>
>>:
 >
 >     Does anyone need more time to get packages built for the
5.0.1 release?
 >     I am hoping to release on Sunday if possible.  Please let me
know if you
 >     need any additional time.
 >
 >     Cheers,
 >
 >     Wayne
 >
 >     ___
 >     Mailing list: https://launchpad.net/~kicad-developers

 >     
 >     Post to     : kicad-developers@lists.launchpad.net

 >     >
 >     Unsubscribe : https://launchpad.net/~kicad-developers

 >     
 >     More help   : https://help.launchpad.net/ListHelp
 >

___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Adam Wolf]

I think there are some 5.0.1s already up for download... Any issue just
going to 5.0.2?

Adam

On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh  wrote:

> I'm fine with pushing the release back another week.  I would rather not
> release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
> breaking Eagle import is not good.  I see one of two options here.
> Retag 5.0.1 with the current changes or release 5.0.2 immediately.  I
> don't know which is more work for our packagers so I am open to either
> option.  Please let me know what works best for you and I will go with
> that option.
>
> Cheers,
>
> Wayne
>
> On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> > Hi Wayne, et al-
> >
> > There is a critical bug that I introduced
> > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.  It affects
> > certain Eagle files imports and causes a crash.
> >
> > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra problems.
> >
> > Between this and the footprint wizard, we may wish to announce a 5.0.2
> > sooner rather than later.  Or packagers may wish to pull in the
> > post-5.0.2 tagged commits as patches to their builds before announcement.
> >
> > -S
> >
> > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> > mailto:stambau...@gmail.com>>:
> >
> > Does anyone need more time to get packages built for the 5.0.1
> release?
> > I am hoping to release on Sunday if possible.  Please let me know if
> you
> > need any additional time.
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

I remember that conversation.  We will continue on with 5.0.1 as is.  If
there isn't any other reason to delay, I will make the release
announcement this evening between 7 and 10PM EST with a note about the
Eagle import issue.

Unless there are any other quick hit bug fixes that we want to get in to
the 5.0.2 release, I will tag commit e34dc4ab in the 5.0 repo so we can
start preparing for the next release as soon as possible.  This will be
the shortest time ever between releases for KiCad. ;)

Cheers,

Wayne

On 10/14/2018 12:13 PM, Carsten Schoenert wrote:
> Hello Wayne,
> 
> Am 14.10.18 um 18:05 schrieb Wayne Stambaugh:
>> I'm fine with pushing the release back another week.  I would rather not
>> release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
>> breaking Eagle import is not good.  I see one of two options here.
>> Retag 5.0.1 with the current changes or release 5.0.2 immediately.
> 
> I guess we already had some discussions in the past about re-use of
> existing tags. :P
> Never ever do this, once a tag was happen it is history, don't touch it
> again. Just proceed with the next tagged version.
> 
> 5.0.1 is already uploaded in Debian to unstable and I can't re-use the
> same version for good reasons.
> 
> It's absolutely no problem to re upload a version 5.0.2 at anytime.
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Carsten Schoenert]

Hello Wayne,

Am 14.10.18 um 18:05 schrieb Wayne Stambaugh:
> I'm fine with pushing the release back another week.  I would rather not
> release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
> breaking Eagle import is not good.  I see one of two options here.
> Retag 5.0.1 with the current changes or release 5.0.2 immediately.

I guess we already had some discussions in the past about re-use of
existing tags. :P
Never ever do this, once a tag was happen it is history, don't touch it
again. Just proceed with the next tagged version.

5.0.1 is already uploaded in Debian to unstable and I can't re-use the
same version for good reasons.

It's absolutely no problem to re upload a version 5.0.2 at anytime.

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

I'm fine with pushing the release back another week.  I would rather not
release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
breaking Eagle import is not good.  I see one of two options here.
Retag 5.0.1 with the current changes or release 5.0.2 immediately.  I
don't know which is more work for our packagers so I am open to either
option.  Please let me know what works best for you and I will go with
that option.

Cheers,

Wayne

On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
> Hi Wayne, et al-
> 
> There is a critical bug that I introduced
> with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.  It affects
> certain Eagle files imports and causes a crash.
> 
> I've fixed this in the 5.0.2 tree.  I'm sorry for the extra problems.
> 
> Between this and the footprint wizard, we may wish to announce a 5.0.2
> sooner rather than later.  Or packagers may wish to pull in the
> post-5.0.2 tagged commits as patches to their builds before announcement.
> 
> -S
> 
> Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
> mailto:stambau...@gmail.com>>:
> 
> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible.  Please let me know if you
> need any additional time.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Seth Hillbrand]

Hi Wayne, et al-

There is a critical bug that I introduced
with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.  It affects
certain Eagle files imports and causes a crash.

I've fixed this in the 5.0.2 tree.  I'm sorry for the extra problems.

Between this and the footprint wizard, we may wish to announce a 5.0.2
sooner rather than later.  Or packagers may wish to pull in the post-5.0.2
tagged commits as patches to their builds before announcement.

-S

Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible.  Please let me know if you
> need any additional time.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Jean-Samuel Reynaud]

PPA (Linux ubuntu). Should be ready tomorrow.

Le 12/10/2018 à 14:38, Wayne Stambaugh a écrit :
> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible.  Please let me know if you
> need any additional time.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Adam Wolf]

MacOS builds should be up Saturday night.  I am hoping to update the
nightly build box, but even if that doesn't happen, i'll create the build
in the VM and upload it that way.

Adam

On Fri, Oct 12, 2018 at 7:57 AM Steven A. Falco 
wrote:

> I just kicked off the Fedora builds about 1 minute ago.  Should be ready
> in an hour or so. :-)
>
> Steve
>
> On 10/12/18 8:38 AM, Wayne Stambaugh wrote:
> > Does anyone need more time to get packages built for the 5.0.1 release?
> > I am hoping to release on Sunday if possible.  Please let me know if you
> > need any additional time.
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release status.

[Steven A. Falco]

I just kicked off the Fedora builds about 1 minute ago.  Should be ready in an 
hour or so. :-)

Steve

On 10/12/18 8:38 AM, Wayne Stambaugh wrote:
> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible.  Please let me know if you
> need any additional time.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.0.1 release status.

[Wayne Stambaugh]

Does anyone need more time to get packages built for the 5.0.1 release?
I am hoping to release on Sunday if possible.  Please let me know if you
need any additional time.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Wayne Stambaugh]

This is great news.  There is one outstanding issue so I should be able
to tag 5.0.1 in the next 24 hours.  Thanks again everyone for your efforts.

Cheers,

Wayne

On 09/29/2018 05:52 PM, Jeff Young wrote:
> Great news!
> 
>> On 29 Sep 2018, at 22:20, Adam Wolf > > wrote:
>>
>> I was able to run the kicad mac packaging regression tests without any
>> issues.
>>
>> I think we're OK!
>>
>> On Sat, Sep 29, 2018 at 3:29 PM Seth Hillbrand > > wrote:
>>
>> Ah, so this may have been a tempest in a teapot.
>>
>> I've only been able to recreate/force an error with the 5.0.0
>> stable build under Mojave.  Does not recreate for 5.0.1 nightly
>> build.  And I can't downgrade to check whether the issue existed
>> under 10.13.  Adam is running his regression checks to verify
>> nothing has changed.  
>>
>> In the meantime, I'm going to finalize the SEGZONE fix for that
>> last bug report.  Should be set for tomorrow if we still want to
>> kick this out on schedule.
>>
>> -S
>>
>> Am Sa., 29. Sep. 2018 um 01:11 Uhr schrieb Bernhard Stegmaier
>> mailto:stegma...@sw-systems.de>>:
>>
>> I did switch to Mojave almost all of my machines.
>> My (own) old builds run without any problem on all of the
>> Mojave machines.
>>
>> I just tried the latest nightly and it also works for me.
>> Only thing I have is that it sometimes doesn’t work on first
>> start (nothing happens) but if I try again.
>> But, that’s something that I always had with the official
>> builds… don’t know what the issues is here (I guess something
>> with the security settings).
>>
>> More details on this?
>>
>>
>> Regards
>> Bernhard
>>
>>> On 29. Sep 2018, at 03:50, Adam Wolf
>>> >> > wrote:
>>>
>>> I am not 100% up to speed on what's broken yet.
>>>
>>> Just for clarifications, we have to compile our nightly
>>> builds with the oldest SDK we want to support, not the
>>> newest.  The issues we've had when 10.11, 10.12, and 10.13
>>> came out were all issues where users on the new version were
>>> unable to compile KiCad without special patches (either to
>>> KiCad or to the dependencies)
>>>
>>> I am surprised we have issues running our old binaries rather
>>> than in compilation, but in computers, not only do things not
>>> work consistently, they don't even break consistently! :)
>>>
>>>
>>> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf
>>> >> > wrote:
>>>
>>> I've been out on business travel this week so I haven't
>>> been able to attend to this at all.  This might not be a
>>> hard problem to fix, but sometimes it takes a bit as it
>>> can be an issue in a dependency.
>>>
>>> Between Seth and I this weekend I'm pretty sure we can
>>> get a good handle on the problem, but solving it might
>>> take a few more days.
>>>
>>> Adam
>>>
>>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand
>>> mailto:s...@hillbrand.org>> wrote:
>>>
>>> Hi Devs-
>>>
>>> We currently have an issue where KiCad does not run
>>> at all on MacOS Mojave that was just released.  It
>>> may just be a matter of re-running the full compile
>>> using the Mojave SDK but we should get that running
>>> on our nightly builds.
>>>
>>> This normally might not be that big of an issue but
>>> the MacOS releases are free downloads and get pushed
>>> pretty hard with pop-ups, so I expect many users will
>>> upgrade soon with no downgrade path.
>>>
>>> I know we were hoping to tag 5.0.1 this weekend but
>>> can we see if there need to be any post-fixes to get
>>> the Mac building for Mojave before we do that?
>>>
>>> Thanks-
>>> Seth
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> 
>>> Post to     : kicad-developers@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> 
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> 

Re: [Kicad-developers] 5.0.1 Release Q

[Wayne Stambaugh]

Hey Seth,

I can hold off tagging 5.0.1 until tomorrow if that helps.  I don't
think 24 hours is going to be a huge setback.

Cheers,

Wayne

On 09/29/2018 11:16 PM, Seth Hillbrand wrote:
> Am Sa., 29. Sep. 2018 um 06:36 Uhr schrieb Wayne Stambaugh
> mailto:stambau...@gmail.com>>:
> 
> We still have some time because as of right now we still have one
> outstanding critical bug report[1] which Seth is working on.  I'm
> willing to push this off for another week to allow macos devs to come up
> with a solution.  Are there any other concerns?
> 
> 
> Hi Wayne-
> 
> A patch for the SEGZONE issue and porting the SEGZONE delete tool to GAL
> has been pushed[0].
> 
> I would like to get the disambiguation/zone selection issue [1] fixed in
> this release as well because the heuristic pruning has resulted in a few
> reports[2][3].  Tom has said he'll have a chance to look at the patch
> this weekend but if he doesn't, we shouldn't delay 5.0.1 for this.  If
> he's able to look it over, then I'd like to include it.
> 
> -Seth
> 
> [0] 
> https://git.launchpad.net/kicad/commit/?id=59723ce3ab2988e9008eaaa5554d1707e7261f2b
> [1] https://bugs.launchpad.net/kicad/+bug/1753153
> [2] https://bugs.launchpad.net/kicad/+bug/1495355
> [3] https://bugs.launchpad.net/kicad/+bug/1789578

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Seth Hillbrand]

Am Sa., 29. Sep. 2018 um 06:36 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> We still have some time because as of right now we still have one
> outstanding critical bug report[1] which Seth is working on.  I'm
> willing to push this off for another week to allow macos devs to come up
> with a solution.  Are there any other concerns?
>

Hi Wayne-

A patch for the SEGZONE issue and porting the SEGZONE delete tool to GAL
has been pushed[0].

I would like to get the disambiguation/zone selection issue [1] fixed in
this release as well because the heuristic pruning has resulted in a few
reports[2][3].  Tom has said he'll have a chance to look at the patch this
weekend but if he doesn't, we shouldn't delay 5.0.1 for this.  If he's able
to look it over, then I'd like to include it.

-Seth

[0]
https://git.launchpad.net/kicad/commit/?id=59723ce3ab2988e9008eaaa5554d1707e7261f2b
[1] https://bugs.launchpad.net/kicad/+bug/1753153
[2] https://bugs.launchpad.net/kicad/+bug/1495355
[3] https://bugs.launchpad.net/kicad/+bug/1789578
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Jeff Young]

Great news!

> On 29 Sep 2018, at 22:20, Adam Wolf  wrote:
> 
> I was able to run the kicad mac packaging regression tests without any issues.
> 
> I think we're OK!
> 
> On Sat, Sep 29, 2018 at 3:29 PM Seth Hillbrand  > wrote:
> Ah, so this may have been a tempest in a teapot.
> 
> I've only been able to recreate/force an error with the 5.0.0 stable build 
> under Mojave.  Does not recreate for 5.0.1 nightly build.  And I can't 
> downgrade to check whether the issue existed under 10.13.  Adam is running 
> his regression checks to verify nothing has changed.  
> 
> In the meantime, I'm going to finalize the SEGZONE fix for that last bug 
> report.  Should be set for tomorrow if we still want to kick this out on 
> schedule.
> 
> -S
> 
> Am Sa., 29. Sep. 2018 um 01:11 Uhr schrieb Bernhard Stegmaier 
> mailto:stegma...@sw-systems.de>>:
> I did switch to Mojave almost all of my machines.
> My (own) old builds run without any problem on all of the Mojave machines.
> 
> I just tried the latest nightly and it also works for me.
> Only thing I have is that it sometimes doesn’t work on first start (nothing 
> happens) but if I try again.
> But, that’s something that I always had with the official builds… don’t know 
> what the issues is here (I guess something with the security settings).
> 
> More details on this?
> 
> 
> Regards
> Bernhard
> 
>> On 29. Sep 2018, at 03:50, Adam Wolf > > wrote:
>> 
>> I am not 100% up to speed on what's broken yet.
>> 
>> Just for clarifications, we have to compile our nightly builds with the 
>> oldest SDK we want to support, not the newest.  The issues we've had when 
>> 10.11, 10.12, and 10.13 came out were all issues where users on the new 
>> version were unable to compile KiCad without special patches (either to 
>> KiCad or to the dependencies)
>> 
>> I am surprised we have issues running our old binaries rather than in 
>> compilation, but in computers, not only do things not work consistently, 
>> they don't even break consistently! :)
>> 
>> 
>> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf > > wrote:
>> I've been out on business travel this week so I haven't been able to attend 
>> to this at all.  This might not be a hard problem to fix, but sometimes it 
>> takes a bit as it can be an issue in a dependency.
>> 
>> Between Seth and I this weekend I'm pretty sure we can get a good handle on 
>> the problem, but solving it might take a few more days.
>> 
>> Adam
>> 
>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand > > wrote:
>> Hi Devs-
>> 
>> We currently have an issue where KiCad does not run at all on MacOS Mojave 
>> that was just released.  It may just be a matter of re-running the full 
>> compile using the Mojave SDK but we should get that running on our nightly 
>> builds.
>> 
>> This normally might not be that big of an issue but the MacOS releases are 
>> free downloads and get pushed pretty hard with pop-ups, so I expect many 
>> users will upgrade soon with no downgrade path.
>> 
>> I know we were hoping to tag 5.0.1 this weekend but can we see if there need 
>> to be any post-fixes to get the Mac building for Mojave before we do that?
>> 
>> Thanks-
>> Seth
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers 
>> 
>> Post to : kicad-developers@lists.launchpad.net 
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers 
>> 
>> More help   : https://help.launchpad.net/ListHelp 
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers 
>> 
>> Post to : kicad-developers@lists.launchpad.net 
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers 
>> 
>> More help   : https://help.launchpad.net/ListHelp 
>> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Adam Wolf]

I was able to run the kicad mac packaging regression tests without any
issues.

I think we're OK!

On Sat, Sep 29, 2018 at 3:29 PM Seth Hillbrand  wrote:

> Ah, so this may have been a tempest in a teapot.
>
> I've only been able to recreate/force an error with the 5.0.0 stable build
> under Mojave.  Does not recreate for 5.0.1 nightly build.  And I can't
> downgrade to check whether the issue existed under 10.13.  Adam is running
> his regression checks to verify nothing has changed.
>
> In the meantime, I'm going to finalize the SEGZONE fix for that last bug
> report.  Should be set for tomorrow if we still want to kick this out on
> schedule.
>
> -S
>
> Am Sa., 29. Sep. 2018 um 01:11 Uhr schrieb Bernhard Stegmaier <
> stegma...@sw-systems.de>:
>
>> I did switch to Mojave almost all of my machines.
>> My (own) old builds run without any problem on all of the Mojave machines.
>>
>> I just tried the latest nightly and it also works for me.
>> Only thing I have is that it sometimes doesn’t work on first start
>> (nothing happens) but if I try again.
>> But, that’s something that I always had with the official builds… don’t
>> know what the issues is here (I guess something with the security settings).
>>
>> More details on this?
>>
>>
>> Regards
>> Bernhard
>>
>> On 29. Sep 2018, at 03:50, Adam Wolf 
>> wrote:
>>
>> I am not 100% up to speed on what's broken yet.
>>
>> Just for clarifications, we have to compile our nightly builds with the
>> oldest SDK we want to support, not the newest.  The issues we've had when
>> 10.11, 10.12, and 10.13 came out were all issues where users on the new
>> version were unable to compile KiCad without special patches (either to
>> KiCad or to the dependencies)
>>
>> I am surprised we have issues running our old binaries rather than in
>> compilation, but in computers, not only do things not work consistently,
>> they don't even break consistently! :)
>>
>>
>> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf 
>> wrote:
>>
>>> I've been out on business travel this week so I haven't been able to
>>> attend to this at all.  This might not be a hard problem to fix, but
>>> sometimes it takes a bit as it can be an issue in a dependency.
>>>
>>> Between Seth and I this weekend I'm pretty sure we can get a good handle
>>> on the problem, but solving it might take a few more days.
>>>
>>> Adam
>>>
>>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand 
>>> wrote:
>>>
 Hi Devs-

 We currently have an issue where KiCad does not run at all on MacOS
 Mojave that was just released.  It may just be a matter of re-running the
 full compile using the Mojave SDK but we should get that running on our
 nightly builds.

 This normally might not be that big of an issue but the MacOS releases
 are free downloads and get pushed pretty hard with pop-ups, so I expect
 many users will upgrade soon with no downgrade path.

 I know we were hoping to tag 5.0.1 this weekend but can we see if there
 need to be any post-fixes to get the Mac building for Mojave before we do
 that?

 Thanks-
 Seth
 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp

>>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Seth Hillbrand]

Ah, so this may have been a tempest in a teapot.

I've only been able to recreate/force an error with the 5.0.0 stable build
under Mojave.  Does not recreate for 5.0.1 nightly build.  And I can't
downgrade to check whether the issue existed under 10.13.  Adam is running
his regression checks to verify nothing has changed.

In the meantime, I'm going to finalize the SEGZONE fix for that last bug
report.  Should be set for tomorrow if we still want to kick this out on
schedule.

-S

Am Sa., 29. Sep. 2018 um 01:11 Uhr schrieb Bernhard Stegmaier <
stegma...@sw-systems.de>:

> I did switch to Mojave almost all of my machines.
> My (own) old builds run without any problem on all of the Mojave machines.
>
> I just tried the latest nightly and it also works for me.
> Only thing I have is that it sometimes doesn’t work on first start
> (nothing happens) but if I try again.
> But, that’s something that I always had with the official builds… don’t
> know what the issues is here (I guess something with the security settings).
>
> More details on this?
>
>
> Regards
> Bernhard
>
> On 29. Sep 2018, at 03:50, Adam Wolf 
> wrote:
>
> I am not 100% up to speed on what's broken yet.
>
> Just for clarifications, we have to compile our nightly builds with the
> oldest SDK we want to support, not the newest.  The issues we've had when
> 10.11, 10.12, and 10.13 came out were all issues where users on the new
> version were unable to compile KiCad without special patches (either to
> KiCad or to the dependencies)
>
> I am surprised we have issues running our old binaries rather than in
> compilation, but in computers, not only do things not work consistently,
> they don't even break consistently! :)
>
>
> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf 
> wrote:
>
>> I've been out on business travel this week so I haven't been able to
>> attend to this at all.  This might not be a hard problem to fix, but
>> sometimes it takes a bit as it can be an issue in a dependency.
>>
>> Between Seth and I this weekend I'm pretty sure we can get a good handle
>> on the problem, but solving it might take a few more days.
>>
>> Adam
>>
>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand 
>> wrote:
>>
>>> Hi Devs-
>>>
>>> We currently have an issue where KiCad does not run at all on MacOS
>>> Mojave that was just released.  It may just be a matter of re-running the
>>> full compile using the Mojave SDK but we should get that running on our
>>> nightly builds.
>>>
>>> This normally might not be that big of an issue but the MacOS releases
>>> are free downloads and get pushed pretty hard with pop-ups, so I expect
>>> many users will upgrade soon with no downgrade path.
>>>
>>> I know we were hoping to tag 5.0.1 this weekend but can we see if there
>>> need to be any post-fixes to get the Mac building for Mojave before we do
>>> that?
>>>
>>> Thanks-
>>> Seth
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Wayne Stambaugh]

We still have some time because as of right now we still have one
outstanding critical bug report[1] which Seth is working on.  I'm
willing to push this off for another week to allow macos devs to come up
with a solution.  Are there any other concerns?

Cheers,

Wayne

[1]: https://bugs.launchpad.net/kicad/+bug/1794571

On 09/29/2018 04:10 AM, Bernhard Stegmaier wrote:
> I did switch to Mojave almost all of my machines.
> My (own) old builds run without any problem on all of the Mojave machines.
> 
> I just tried the latest nightly and it also works for me.
> Only thing I have is that it sometimes doesn’t work on first start
> (nothing happens) but if I try again.
> But, that’s something that I always had with the official builds… don’t
> know what the issues is here (I guess something with the security settings).
> 
> More details on this?
> 
> 
> Regards
> Bernhard
> 
>> On 29. Sep 2018, at 03:50, Adam Wolf > > wrote:
>>
>> I am not 100% up to speed on what's broken yet.
>>
>> Just for clarifications, we have to compile our nightly builds with
>> the oldest SDK we want to support, not the newest.  The issues we've
>> had when 10.11, 10.12, and 10.13 came out were all issues where users
>> on the new version were unable to compile KiCad without special
>> patches (either to KiCad or to the dependencies)
>>
>> I am surprised we have issues running our old binaries rather than in
>> compilation, but in computers, not only do things not work
>> consistently, they don't even break consistently! :)
>>
>>
>> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf
>> mailto:adamw...@feelslikeburning.com>>
>> wrote:
>>
>> I've been out on business travel this week so I haven't been able
>> to attend to this at all.  This might not be a hard problem to
>> fix, but sometimes it takes a bit as it can be an issue in a
>> dependency.
>>
>> Between Seth and I this weekend I'm pretty sure we can get a good
>> handle on the problem, but solving it might take a few more days.
>>
>> Adam
>>
>> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand > > wrote:
>>
>> Hi Devs-
>>
>> We currently have an issue where KiCad does not run at all on
>> MacOS Mojave that was just released.  It may just be a matter
>> of re-running the full compile using the Mojave SDK but we
>> should get that running on our nightly builds.
>>
>> This normally might not be that big of an issue but the MacOS
>> releases are free downloads and get pushed pretty hard with
>> pop-ups, so I expect many users will upgrade soon with no
>> downgrade path.
>>
>> I know we were hoping to tag 5.0.1 this weekend but can we see
>> if there need to be any post-fixes to get the Mac building for
>> Mojave before we do that?
>>
>> Thanks-
>> Seth
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> 
>> Post to     : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> 
>> More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> 
>> Post to : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> 
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Bernhard Stegmaier]

I did switch to Mojave almost all of my machines.
My (own) old builds run without any problem on all of the Mojave machines.

I just tried the latest nightly and it also works for me.
Only thing I have is that it sometimes doesn’t work on first start (nothing 
happens) but if I try again.
But, that’s something that I always had with the official builds… don’t know 
what the issues is here (I guess something with the security settings).

More details on this?


Regards
Bernhard

> On 29. Sep 2018, at 03:50, Adam Wolf  wrote:
> 
> I am not 100% up to speed on what's broken yet.
> 
> Just for clarifications, we have to compile our nightly builds with the 
> oldest SDK we want to support, not the newest.  The issues we've had when 
> 10.11, 10.12, and 10.13 came out were all issues where users on the new 
> version were unable to compile KiCad without special patches (either to KiCad 
> or to the dependencies)
> 
> I am surprised we have issues running our old binaries rather than in 
> compilation, but in computers, not only do things not work consistently, they 
> don't even break consistently! :)
> 
> 
> On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf  > wrote:
> I've been out on business travel this week so I haven't been able to attend 
> to this at all.  This might not be a hard problem to fix, but sometimes it 
> takes a bit as it can be an issue in a dependency.
> 
> Between Seth and I this weekend I'm pretty sure we can get a good handle on 
> the problem, but solving it might take a few more days.
> 
> Adam
> 
> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand  > wrote:
> Hi Devs-
> 
> We currently have an issue where KiCad does not run at all on MacOS Mojave 
> that was just released.  It may just be a matter of re-running the full 
> compile using the Mojave SDK but we should get that running on our nightly 
> builds.
> 
> This normally might not be that big of an issue but the MacOS releases are 
> free downloads and get pushed pretty hard with pop-ups, so I expect many 
> users will upgrade soon with no downgrade path.
> 
> I know we were hoping to tag 5.0.1 this weekend but can we see if there need 
> to be any post-fixes to get the Mac building for Mojave before we do that?
> 
> Thanks-
> Seth
> ___
> Mailing list: https://launchpad.net/~kicad-developers 
> 
> Post to : kicad-developers@lists.launchpad.net 
> 
> Unsubscribe : https://launchpad.net/~kicad-developers 
> 
> More help   : https://help.launchpad.net/ListHelp 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Adam Wolf]

I am not 100% up to speed on what's broken yet.

Just for clarifications, we have to compile our nightly builds with the
oldest SDK we want to support, not the newest.  The issues we've had when
10.11, 10.12, and 10.13 came out were all issues where users on the new
version were unable to compile KiCad without special patches (either to
KiCad or to the dependencies)

I am surprised we have issues running our old binaries rather than in
compilation, but in computers, not only do things not work consistently,
they don't even break consistently! :)


On Fri, Sep 28, 2018 at 8:40 PM Adam Wolf 
wrote:

> I've been out on business travel this week so I haven't been able to
> attend to this at all.  This might not be a hard problem to fix, but
> sometimes it takes a bit as it can be an issue in a dependency.
>
> Between Seth and I this weekend I'm pretty sure we can get a good handle
> on the problem, but solving it might take a few more days.
>
> Adam
>
> On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand  wrote:
>
>> Hi Devs-
>>
>> We currently have an issue where KiCad does not run at all on MacOS
>> Mojave that was just released.  It may just be a matter of re-running the
>> full compile using the Mojave SDK but we should get that running on our
>> nightly builds.
>>
>> This normally might not be that big of an issue but the MacOS releases
>> are free downloads and get pushed pretty hard with pop-ups, so I expect
>> many users will upgrade soon with no downgrade path.
>>
>> I know we were hoping to tag 5.0.1 this weekend but can we see if there
>> need to be any post-fixes to get the Mac building for Mojave before we do
>> that?
>>
>> Thanks-
>> Seth
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 Release Q

[Adam Wolf]

I've been out on business travel this week so I haven't been able to attend
to this at all.  This might not be a hard problem to fix, but sometimes it
takes a bit as it can be an issue in a dependency.

Between Seth and I this weekend I'm pretty sure we can get a good handle on
the problem, but solving it might take a few more days.

Adam

On Fri, Sep 28, 2018 at 4:16 PM Seth Hillbrand  wrote:

> Hi Devs-
>
> We currently have an issue where KiCad does not run at all on MacOS Mojave
> that was just released.  It may just be a matter of re-running the full
> compile using the Mojave SDK but we should get that running on our nightly
> builds.
>
> This normally might not be that big of an issue but the MacOS releases are
> free downloads and get pushed pretty hard with pop-ups, so I expect many
> users will upgrade soon with no downgrade path.
>
> I know we were hoping to tag 5.0.1 this weekend but can we see if there
> need to be any post-fixes to get the Mac building for Mojave before we do
> that?
>
> Thanks-
> Seth
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.0.1 Release Q

[Seth Hillbrand]

Hi Devs-

We currently have an issue where KiCad does not run at all on MacOS Mojave
that was just released.  It may just be a matter of re-running the full
compile using the Mojave SDK but we should get that running on our nightly
builds.

This normally might not be that big of an issue but the MacOS releases are
free downloads and get pushed pretty hard with pop-ups, so I expect many
users will upgrade soon with no downgrade path.

I know we were hoping to tag 5.0.1 this weekend but can we see if there
need to be any post-fixes to get the Mac building for Mojave before we do
that?

Thanks-
Seth
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Tomasz Wlostowski]

On 22/09/18 15:10, Wayne Stambaugh wrote:
>  There is one outstanding critical bug [1]
> that needs to be fixed before this can happen.  Tom, have you made any
> progress on this?

Hi Wayne,

I've already fixed it, just need to rebase on the 5.0 branch (if nothing
unexpected happens, I'll do it tomorrow morning).

Tom

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

Seth and JP,

On 09/23/2018 03:41 AM, jp charras wrote:

Le 22/09/2018 à 20:09, Seth Hillbrand a écrit :

Hi Wayne/JP-

Am Sa., 22. Sep. 2018 um 10:22 Uhr schrieb Wayne Stambaugh
mailto:stambau...@gmail.com>>:


 You may want to coordinate with JP on this.  I believe he is working on
 a fix as well.  I also have a few ideas that I would like to discuss
 about the current design going forward.  I'm going to be busy the rest
 of the day but tomorrow I will have some time to go over some of my
 thoughts about the current situation.


Just seeing this.  1778564 turned out to be a clang-specific problem.

Long-term, a lot of this probably goes away if we incorporate kicad2step
internally but I'll be curious to hear other thoughts/options.

-S



I recently made a few tests on Linux, and find there are many issues
with filenames (and strings) using non ascii7 chars.

These issues are encountered when kicad2step is a console application
using a wxAppConsole application.

When a similar (nearly the same) code run using wxApp, these problems
are gone.

For instance, on my Linux 14.04 French, inside a wxAppConsole:
"wxLogMessage( "12à" );" segfaults.

And wxPrint, wxFile, wxFileName have serious issues.
(wxLogMessage and wxPrint print nothing if a string contains unicode chars)

Inside a wxApp, it works as expected.

Currently, I have a modified source (only for tests)  where I removed
all wxLogMessage calls and replaced by a Report(wxStrin& msg) call to
avoid issues in wxLogMessage .

And I am waiting for Wayne's ideas.

Of course incorporate kicad2step internally will fix these non ascii7
char issues.

But there is a difficulty: Opencascade prints messages on a console when
running:
How to collect them if we want to print them inside a window in Kicad.

An alternate option (I tested it) is modifying kicad2step to use wxApp,
and run it like now as external application.

I don't think it can be done for 5.01 release.



I would prefer we spend the minimal amount of time required to fix the 
current kicad2step issues as best we can.  I never been a big fan of 
calling an external app to create the mcad files.  I suspect there are 
some users who will want to continue to use the stand alone app but I 
really do not want to continue to support it over the long run.  The 
current design was always meant to be a stop gap measure to provide 
support for step and iges output.


I would like to see us fix this in three phases.

Phase 1, remove external process call:

Copy the pcb/ and sexpr/ from the kicad2 step folder into the common/ 
folder.


Create a new KICAD2MCAD object that only handles the export options in 
the dialog and accepts an optional REPORTER object to dump to the dialog 
info panel.


Replace all instances of wxLogMessage in the step export code to us the 
optional REPORTER object.


Since OCE has a known issue with non-ascii characters, check if the 
output file name contains non-ascii characters and write to a temporary 
file and then copy the temporary file to the proper file name using the 
correct file name (thanks to JP for that suggestion).


Phase 2: remove dependency of external s-expr parser.

Pass a BOARD object to the KICAD2MCAD object and use the actual board 
objects to create generate the oce call information rather than the 
s-expr object.


Remove the s-expr code as it willl no longer be required.

Phase 3: command line access to the exporter

Add command line support for the step exporter to pcbnew.

Remove the stand alone kicad2step code.

I don't think phase 1 will be all that difficult but it will be some 
busy to replace wxLogMessage with REPORTER.  Phase two will require a 
lot more effort to go through all of the oce output code and replace the 
current parser with the BOARD objects.  Phase 3 may be tricky if we 
cannot figure out a way to run the export code without displaying the 
frame window but I haven't looked at this yet so I could be wrong.


As far as timing, I would like to see Phase 1 be done as part of 5.1. 
Phases 2 and 3 can be done as part of v6 or later.


Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[jp charras]

Le 22/09/2018 à 20:09, Seth Hillbrand a écrit :
> Hi Wayne/JP-
> 
> Am Sa., 22. Sep. 2018 um 10:22 Uhr schrieb Wayne Stambaugh
> mailto:stambau...@gmail.com>>:
> 
> 
> You may want to coordinate with JP on this.  I believe he is working on
> a fix as well.  I also have a few ideas that I would like to discuss
> about the current design going forward.  I'm going to be busy the rest
> of the day but tomorrow I will have some time to go over some of my
> thoughts about the current situation.
> 
> 
> Just seeing this.  1778564 turned out to be a clang-specific problem. 
> 
> Long-term, a lot of this probably goes away if we incorporate kicad2step
> internally but I'll be curious to hear other thoughts/options.
> 
> -S


I recently made a few tests on Linux, and find there are many issues
with filenames (and strings) using non ascii7 chars.

These issues are encountered when kicad2step is a console application
using a wxAppConsole application.

When a similar (nearly the same) code run using wxApp, these problems
are gone.

For instance, on my Linux 14.04 French, inside a wxAppConsole:
"wxLogMessage( "12à" );" segfaults.

And wxPrint, wxFile, wxFileName have serious issues.
(wxLogMessage and wxPrint print nothing if a string contains unicode chars)

Inside a wxApp, it works as expected.

Currently, I have a modified source (only for tests)  where I removed
all wxLogMessage calls and replaced by a Report(wxStrin& msg) call to
avoid issues in wxLogMessage .

And I am waiting for Wayne's ideas.

Of course incorporate kicad2step internally will fix these non ascii7
char issues.

But there is a difficulty: Opencascade prints messages on a console when
running:
How to collect them if we want to print them inside a window in Kicad.

An alternate option (I tested it) is modifying kicad2step to use wxApp,
and run it like now as external application.

I don't think it can be done for 5.01 release.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Seth Hillbrand]

Hi Wayne/JP-

Am Sa., 22. Sep. 2018 um 10:22 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

>
> You may want to coordinate with JP on this.  I believe he is working on
> a fix as well.  I also have a few ideas that I would like to discuss
> about the current design going forward.  I'm going to be busy the rest
> of the day but tomorrow I will have some time to go over some of my
> thoughts about the current situation.
>

Just seeing this.  1778564 turned out to be a clang-specific problem.

Long-term, a lot of this probably goes away if we incorporate kicad2step
internally but I'll be curious to hear other thoughts/options.

-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

Hey Seth

On 09/22/2018 10:40 AM, Seth Hillbrand wrote:

Hi Wayne-

Am Sa., 22. Sep. 2018 um 06:11 Uhr schrieb Wayne Stambaugh 
mailto:stambau...@gmail.com>>:


I would like try to get a 5.0.1 release out next week end and then allow
another week for our package devs to prep release packages before making
the official release announcement if at all possible.  There are a lot a
bug fixes in 5.0.1 that should be made available for users who don't
want to bleed on the edge.  There is one outstanding critical bug [1]
that needs to be fixed before this can happen.  Tom, have you made any
progress on this?  I am willing to push the other two bugs[2][3] to
5.0.2 or 5.1 as they are both likely to require some user testing before
being released as stable.  Are there any other outstanding issues at the
moment that I may have missed?  As always, thank you everyone for your
efforts.


This is great news! I have one more issue [1] that I'd like to address 
in the 5.0.1 release.  More kicad2step fun.


-S

[1] https://bugs.launchpad.net/kicad/+bug/1778564


You may want to coordinate with JP on this.  I believe he is working on 
a fix as well.  I also have a few ideas that I would like to discuss 
about the current design going forward.  I'm going to be busy the rest 
of the day but tomorrow I will have some time to go over some of my 
thoughts about the current situation.


Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Seth Hillbrand]

Hi Wayne-

Am Sa., 22. Sep. 2018 um 06:11 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> I would like try to get a 5.0.1 release out next week end and then allow
> another week for our package devs to prep release packages before making
> the official release announcement if at all possible.  There are a lot a
> bug fixes in 5.0.1 that should be made available for users who don't
> want to bleed on the edge.  There is one outstanding critical bug [1]
> that needs to be fixed before this can happen.  Tom, have you made any
> progress on this?  I am willing to push the other two bugs[2][3] to
> 5.0.2 or 5.1 as they are both likely to require some user testing before
> being released as stable.  Are there any other outstanding issues at the
> moment that I may have missed?  As always, thank you everyone for your
> efforts.
>

This is great news! I have one more issue [1] that I'd like to address in
the 5.0.1 release.  More kicad2step fun.

-S

[1] https://bugs.launchpad.net/kicad/+bug/1778564
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

I would like try to get a 5.0.1 release out next week end and then allow
another week for our package devs to prep release packages before making
the official release announcement if at all possible.  There are a lot a
bug fixes in 5.0.1 that should be made available for users who don't
want to bleed on the edge.  There is one outstanding critical bug [1]
that needs to be fixed before this can happen.  Tom, have you made any
progress on this?  I am willing to push the other two bugs[2][3] to
5.0.2 or 5.1 as they are both likely to require some user testing before
being released as stable.  Are there any other outstanding issues at the
moment that I may have missed?  As always, thank you everyone for your
efforts.

Cheers,

Wayne

[1]: https://bugs.launchpad.net/kicad/+bug/1793110
[2]: https://bugs.launchpad.net/kicad/+bug/1690780
[3]: https://bugs.launchpad.net/kicad/+bug/1791280

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Rene Pöschl]

Hi,

I doubt we need to rename the lib. It might be better to declare it as 
deprecated (remove it from the default library table and place a note in 
the readme file)


A new library can definitely be created that is build around the ngspice 
features that come with version 5 (the pspice lib is quite old and not 
really build for that implementation)

The library name is best discussed over at github.

On 30/08/18 04:41, Evan Shultz wrote:
There is one library name I'm concerned about. See 
https://github.com/KiCad/kicad-symbols/issues/451#issuecomment-378701973. 
This would be a breaking change, but if it's important enough to 
change it's likely to only affect a small subset of all KiCad users.


It is "correct" to have a library with symbols for simulation named 
"pspice"? Should the library just be named "spice" or something more 
generic?


On Tue, Aug 28, 2018 at 11:07 AM Rene Pöschl > wrote:


Just to be sure i will ask the other librarians how strict they where
with our policy. (Sadly on the symbol side git is not of much help
so i
really need to rely on their word. I will also make some manual
checks.)

For the future we might think about getting check scripts
developed that
check for changes that would go too far. (To reduce the chance of
human
errors. Some maintainers might be tempted to include one small change
that is slightly across the line. If this happens with enough
frequency
then the sum of all changes could be too much.)

On 28/08/18 19:16, Wayne Stambaugh wrote:
> On 8/28/2018 12:48 PM, Rene Pöschl wrote:
>> Right now we have no changes made that would break projects.
(That is
>> what i meant with "backwards compatibility" I know it is not
quite the
>> right term)
>>
>> Also i thought the cache lib plus rescue dialog should take care of
>> minor changes to symbols if the user does not want to update a
symbol
>> should it be changed.
> Yes, but I do not like depending on the cache.  It's too
fragile.  Once
> the new schematic file format is in place, this will no be an issue.
> Until then, I prefer to error on the side of caution given the cache
> issues we've had in the past.
>
>> It should not even be necessary as we do not allow changes to
symbol pin
>> numbers or positions. (Unless there was a mistake in the symbol.)
>>
>> As we did not include any of the wrongly scaled or wrongly
aligned 3d
>> models in the version 5 library there is also no danger of
damaging the
>> 3d rendering side. (There is a reason why the version 5 3d
model library
>> is a lot smaller compared to the version 4 3d model lib)
>>
>> We do neither allow changing any library names nor do we change
symbol,
>> footprint or 3d model names unless the original name was wrong
enough to
>> be in danger of being confused with a part different to the one
that the
>> object really represents.
>>
>> If you do not intend to include the library then i will lift
the ban on
>> major changes as it does not make any sense in that case to
hold back.
>> (The only reason would be to allow including bugfixes into
future kicad
>> bugfix releases. I would include updating to newer industry
standards as
>> bugfix. The later is the main work being continued on the footprint
>> side. We simply where not done with it with the v5 release but
it was
>> not bad enough to postpone the release.)
> I didn't realize you were keeping tight control of the library
commits.
>   I'm fine with these changes being added to 5.0.1. I would like
to keep
> the libraries relatively stable during the entire 5 stable
series.  For
> version 6, you can make whatever changes you see fit.
>
>>
>> On 28/08/18 18:30, Wayne Stambaugh wrote:
>>> I would be careful with any library improvements during stable
bug fix
>>> releases, particularly for symbol and 3d model libraries which are
>>> linked rather than embedded.  My preference would be to just
use the
>>> same libraries tagged for the 5.0.0 release to keep changes to
user
>>> designs to a minimum.  Users can always download the latest
libraries if
>>> they prefer the bleeding edge.
>>>
>>> On 8/28/2018 12:18 PM, Rene Pöschl wrote:
 Is it planned to include a new version of the libraries as well?
 Right now we ensure that the library is relatively stable so
i think the
 improvements made since the v5 release can easily be included.
 (We do not allow major changes that would break backward
compatibility.
 My plan is to use this rule at least till after the 5.1
release. Maybe
 even until the new file format is well enough implemented to
play around
 with it in the official library.)

Re: [Kicad-developers] 5.0.1 release

[Seth Hillbrand]

Hi Carsten-

Am Mi., 29. Aug. 2018 um 22:38 Uhr schrieb Carsten Schoenert <
c.schoen...@t-online.de>:

> Hello Seth,
>
> Am 29.08.18 um 22:32 schrieb Seth Hillbrand:
> > Hi All-
> >
> > Quick question for packagers:  If we need to re-make a package after
> > 5.0.1 is released, can we use -DKICAD_VERSION_EXTRA=1 when you re-build
> > and increment the number for each subsequent build of the same release?
>
> I'm not sure what you mean by 'If we need to re-make'.


The case I envision is if a package is accidentally built using the wrong
flags and needs to be re-built using the same software source.


> KiCad uses until
> now the semantic versioning [1]. At least what I think about the version
> number. So I my understanding is simply you will increase the PATCH
> version with every fixup release like done in the past. If you create a
> new micro version the version string is simply 'major.minor.patch+1'.
>

Correct!  This version string is my hope.  The KICAD_VERSION_EXTRA=1 define
will make it 'major.minor.patch-1' but I'm happy with packagers using
either.  I really just want to be able to tell from which packaging a bug
report originates.


> > The extra string will be appended to the KICAD_FULL_VERSION and get
> > reported in the bug reports version listing.  This would greatly help to
> > identify issues as well as give users the heads up when there is a newer
> > version that they should be using.
>
> All you need is an unequivocal version, right.


Yes.  I thought to give an example that would accomplish this but I'm very
happy with a different approach that achieves the same unequivocal version
number that includes build revision.  I do not intend for this to be
complicating and I'm very happy with any solution that gets to the same
result.  What I really hope to avoid is the version 5.0.0 situation where
our first step when debugging windows-based KiCad crashes is to ask users
to re-download the same version again.

Best Regards-
Seth
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Carsten Schoenert]

Hello Seth,

Am 29.08.18 um 22:32 schrieb Seth Hillbrand:
> Hi All-
> 
> Quick question for packagers:  If we need to re-make a package after
> 5.0.1 is released, can we use -DKICAD_VERSION_EXTRA=1 when you re-build
> and increment the number for each subsequent build of the same release?

I'm not sure what you mean by 'If we need to re-make'. KiCad uses until
now the semantic versioning [1]. At least what I think about the version
number. So I my understanding is simply you will increase the PATCH
version with every fixup release like done in the past. If you create a
new micro version the version string is simply 'major.minor.patch+1'.

Version numbers are cheap and costs quite nothing. No need to add one
more extra special additional one-time version string in my eyes.

> The extra string will be appended to the KICAD_FULL_VERSION and get
> reported in the bug reports version listing.  This would greatly help to
> identify issues as well as give users the heads up when there is a newer
> version that they should be using.

All you need is an unequivocal version, right. Adding some 'extra'
string makes it more complicated if you would break the existing version
string. People could make mistakes while copying the version string or
even try to manipulate somehow the string. For more clearance you will
need the SHA hash id which is also a bit complicated to trust, git
archive isn't using it for example if you build up an archive from a
tag. So version created that way won't have a hash id in the extra
version info even if you would display a string for this.

[1] https://semver.org/

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Evan Shultz]

There is one library name I'm concerned about. See
https://github.com/KiCad/kicad-symbols/issues/451#issuecomment-378701973.
This would be a breaking change, but if it's important enough to change
it's likely to only affect a small subset of all KiCad users.

It is "correct" to have a library with symbols for simulation named
"pspice"? Should the library just be named "spice" or something more
generic?

On Tue, Aug 28, 2018 at 11:07 AM Rene Pöschl  wrote:

> Just to be sure i will ask the other librarians how strict they where
> with our policy. (Sadly on the symbol side git is not of much help so i
> really need to rely on their word. I will also make some manual checks.)
>
> For the future we might think about getting check scripts developed that
> check for changes that would go too far. (To reduce the chance of human
> errors. Some maintainers might be tempted to include one small change
> that is slightly across the line. If this happens with enough frequency
> then the sum of all changes could be too much.)
>
> On 28/08/18 19:16, Wayne Stambaugh wrote:
> > On 8/28/2018 12:48 PM, Rene Pöschl wrote:
> >> Right now we have no changes made that would break projects. (That is
> >> what i meant with "backwards compatibility" I know it is not quite the
> >> right term)
> >>
> >> Also i thought the cache lib plus rescue dialog should take care of
> >> minor changes to symbols if the user does not want to update a symbol
> >> should it be changed.
> > Yes, but I do not like depending on the cache.  It's too fragile.  Once
> > the new schematic file format is in place, this will no be an issue.
> > Until then, I prefer to error on the side of caution given the cache
> > issues we've had in the past.
> >
> >> It should not even be necessary as we do not allow changes to symbol pin
> >> numbers or positions. (Unless there was a mistake in the symbol.)
> >>
> >> As we did not include any of the wrongly scaled or wrongly aligned 3d
> >> models in the version 5 library there is also no danger of damaging the
> >> 3d rendering side. (There is a reason why the version 5 3d model library
> >> is a lot smaller compared to the version 4 3d model lib)
> >>
> >> We do neither allow changing any library names nor do we change symbol,
> >> footprint or 3d model names unless the original name was wrong enough to
> >> be in danger of being confused with a part different to the one that the
> >> object really represents.
> >>
> >> If you do not intend to include the library then i will lift the ban on
> >> major changes as it does not make any sense in that case to hold back.
> >> (The only reason would be to allow including bugfixes into future kicad
> >> bugfix releases. I would include updating to newer industry standards as
> >> bugfix. The later is the main work being continued on the footprint
> >> side. We simply where not done with it with the v5 release but it was
> >> not bad enough to postpone the release.)
> > I didn't realize you were keeping tight control of the library commits.
> >   I'm fine with these changes being added to 5.0.1.  I would like to keep
> > the libraries relatively stable during the entire 5 stable series.  For
> > version 6, you can make whatever changes you see fit.
> >
> >>
> >> On 28/08/18 18:30, Wayne Stambaugh wrote:
> >>> I would be careful with any library improvements during stable bug fix
> >>> releases, particularly for symbol and 3d model libraries which are
> >>> linked rather than embedded.  My preference would be to just use the
> >>> same libraries tagged for the 5.0.0 release to keep changes to user
> >>> designs to a minimum.  Users can always download the latest libraries
> if
> >>> they prefer the bleeding edge.
> >>>
> >>> On 8/28/2018 12:18 PM, Rene Pöschl wrote:
>  Is it planned to include a new version of the libraries as well?
>  Right now we ensure that the library is relatively stable so i think
> the
>  improvements made since the v5 release can easily be included.
>  (We do not allow major changes that would break backward
> compatibility.
>  My plan is to use this rule at least till after the 5.1 release. Maybe
>  even until the new file format is well enough implemented to play
> around
>  with it in the official library.)
> 
>  On 27/08/18 21:38, Wayne Stambaugh wrote:
> > I would like to get the 5.0.1 release out by the end of September if
> at
> > all possible.  There are still a few open bug reports which need to
> be
> > fixed before we can release this so if you can fix any of the ones
> that
> > do not already have an assignee[1], any help would be appreciated.
> My
> > goal is to have all of the bug reports closed by 9/15 and give the
> > package devs a few weeks before making the release announcement.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]: https://launchpad.net/kicad/+milestone/5.0.1
> >
> > ___
> > Mailing list: 

Re: [Kicad-developers] 5.0.1 release

[Seth Hillbrand]

Hi All-

Quick question for packagers:  If we need to re-make a package after 5.0.1
is released, can we use -DKICAD_VERSION_EXTRA=1 when you re-build and
increment the number for each subsequent build of the same release?

The extra string will be appended to the KICAD_FULL_VERSION and get
reported in the bug reports version listing.  This would greatly help to
identify issues as well as give users the heads up when there is a newer
version that they should be using.

Best-
Seth

Am Mo., 27. Aug. 2018 um 12:39 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> I would like to get the 5.0.1 release out by the end of September if at
> all possible.  There are still a few open bug reports which need to be
> fixed before we can release this so if you can fix any of the ones that
> do not already have an assignee[1], any help would be appreciated.  My
> goal is to have all of the bug reports closed by 9/15 and give the
> package devs a few weeks before making the release announcement.
>
> Cheers,
>
> Wayne
>
> [1]: https://launchpad.net/kicad/+milestone/5.0.1
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Rene Pöschl]

Just to be sure i will ask the other librarians how strict they where 
with our policy. (Sadly on the symbol side git is not of much help so i 
really need to rely on their word. I will also make some manual checks.)


For the future we might think about getting check scripts developed that 
check for changes that would go too far. (To reduce the chance of human 
errors. Some maintainers might be tempted to include one small change 
that is slightly across the line. If this happens with enough frequency 
then the sum of all changes could be too much.)


On 28/08/18 19:16, Wayne Stambaugh wrote:

On 8/28/2018 12:48 PM, Rene Pöschl wrote:

Right now we have no changes made that would break projects. (That is
what i meant with "backwards compatibility" I know it is not quite the
right term)

Also i thought the cache lib plus rescue dialog should take care of
minor changes to symbols if the user does not want to update a symbol
should it be changed.

Yes, but I do not like depending on the cache.  It's too fragile.  Once
the new schematic file format is in place, this will no be an issue.
Until then, I prefer to error on the side of caution given the cache
issues we've had in the past.


It should not even be necessary as we do not allow changes to symbol pin
numbers or positions. (Unless there was a mistake in the symbol.)

As we did not include any of the wrongly scaled or wrongly aligned 3d
models in the version 5 library there is also no danger of damaging the
3d rendering side. (There is a reason why the version 5 3d model library
is a lot smaller compared to the version 4 3d model lib)

We do neither allow changing any library names nor do we change symbol,
footprint or 3d model names unless the original name was wrong enough to
be in danger of being confused with a part different to the one that the
object really represents.

If you do not intend to include the library then i will lift the ban on
major changes as it does not make any sense in that case to hold back.
(The only reason would be to allow including bugfixes into future kicad
bugfix releases. I would include updating to newer industry standards as
bugfix. The later is the main work being continued on the footprint
side. We simply where not done with it with the v5 release but it was
not bad enough to postpone the release.)

I didn't realize you were keeping tight control of the library commits.
  I'm fine with these changes being added to 5.0.1.  I would like to keep
the libraries relatively stable during the entire 5 stable series.  For
version 6, you can make whatever changes you see fit.



On 28/08/18 18:30, Wayne Stambaugh wrote:

I would be careful with any library improvements during stable bug fix
releases, particularly for symbol and 3d model libraries which are
linked rather than embedded.  My preference would be to just use the
same libraries tagged for the 5.0.0 release to keep changes to user
designs to a minimum.  Users can always download the latest libraries if
they prefer the bleeding edge.

On 8/28/2018 12:18 PM, Rene Pöschl wrote:

Is it planned to include a new version of the libraries as well?
Right now we ensure that the library is relatively stable so i think the
improvements made since the v5 release can easily be included.
(We do not allow major changes that would break backward compatibility.
My plan is to use this rule at least till after the 5.1 release. Maybe
even until the new file format is well enough implemented to play around
with it in the official library.)

On 27/08/18 21:38, Wayne Stambaugh wrote:

I would like to get the 5.0.1 release out by the end of September if at
all possible.  There are still a few open bug reports which need to be
fixed before we can release this so if you can fix any of the ones that
do not already have an assignee[1], any help would be appreciated.  My
goal is to have all of the bug reports closed by 9/15 and give the
package devs a few weeks before making the release announcement.

Cheers,

Wayne

[1]: https://launchpad.net/kicad/+milestone/5.0.1

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : http

Re: [Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

On 8/28/2018 12:48 PM, Rene Pöschl wrote:
> Right now we have no changes made that would break projects. (That is
> what i meant with "backwards compatibility" I know it is not quite the
> right term)
> 
> Also i thought the cache lib plus rescue dialog should take care of
> minor changes to symbols if the user does not want to update a symbol
> should it be changed.

Yes, but I do not like depending on the cache.  It's too fragile.  Once
the new schematic file format is in place, this will no be an issue.
Until then, I prefer to error on the side of caution given the cache
issues we've had in the past.

> It should not even be necessary as we do not allow changes to symbol pin
> numbers or positions. (Unless there was a mistake in the symbol.)
> 
> As we did not include any of the wrongly scaled or wrongly aligned 3d
> models in the version 5 library there is also no danger of damaging the
> 3d rendering side. (There is a reason why the version 5 3d model library
> is a lot smaller compared to the version 4 3d model lib)
> 
> We do neither allow changing any library names nor do we change symbol,
> footprint or 3d model names unless the original name was wrong enough to
> be in danger of being confused with a part different to the one that the
> object really represents.
> 
> If you do not intend to include the library then i will lift the ban on
> major changes as it does not make any sense in that case to hold back.
> (The only reason would be to allow including bugfixes into future kicad
> bugfix releases. I would include updating to newer industry standards as
> bugfix. The later is the main work being continued on the footprint
> side. We simply where not done with it with the v5 release but it was
> not bad enough to postpone the release.)

I didn't realize you were keeping tight control of the library commits.
 I'm fine with these changes being added to 5.0.1.  I would like to keep
the libraries relatively stable during the entire 5 stable series.  For
version 6, you can make whatever changes you see fit.

> 
> 
> On 28/08/18 18:30, Wayne Stambaugh wrote:
>> I would be careful with any library improvements during stable bug fix
>> releases, particularly for symbol and 3d model libraries which are
>> linked rather than embedded.  My preference would be to just use the
>> same libraries tagged for the 5.0.0 release to keep changes to user
>> designs to a minimum.  Users can always download the latest libraries if
>> they prefer the bleeding edge.
>>
>> On 8/28/2018 12:18 PM, Rene Pöschl wrote:
>>> Is it planned to include a new version of the libraries as well?
>>> Right now we ensure that the library is relatively stable so i think the
>>> improvements made since the v5 release can easily be included.
>>> (We do not allow major changes that would break backward compatibility.
>>> My plan is to use this rule at least till after the 5.1 release. Maybe
>>> even until the new file format is well enough implemented to play around
>>> with it in the official library.)
>>>
>>> On 27/08/18 21:38, Wayne Stambaugh wrote:
 I would like to get the 5.0.1 release out by the end of September if at
 all possible.  There are still a few open bug reports which need to be
 fixed before we can release this so if you can fix any of the ones that
 do not already have an assignee[1], any help would be appreciated.  My
 goal is to have all of the bug reports closed by 9/15 and give the
 package devs a few weeks before making the release announcement.

 Cheers,

 Wayne

 [1]: https://launchpad.net/kicad/+milestone/5.0.1

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Rene Pöschl]

Right now we have no changes made that would break projects. (That is 
what i meant with "backwards compatibility" I know it is not quite the 
right term)


Also i thought the cache lib plus rescue dialog should take care of 
minor changes to symbols if the user does not want to update a symbol 
should it be changed.
It should not even be necessary as we do not allow changes to symbol pin 
numbers or positions. (Unless there was a mistake in the symbol.)


As we did not include any of the wrongly scaled or wrongly aligned 3d 
models in the version 5 library there is also no danger of damaging the 
3d rendering side. (There is a reason why the version 5 3d model library 
is a lot smaller compared to the version 4 3d model lib)


We do neither allow changing any library names nor do we change symbol, 
footprint or 3d model names unless the original name was wrong enough to 
be in danger of being confused with a part different to the one that the 
object really represents.


If you do not intend to include the library then i will lift the ban on 
major changes as it does not make any sense in that case to hold back. 
(The only reason would be to allow including bugfixes into future kicad 
bugfix releases. I would include updating to newer industry standards as 
bugfix. The later is the main work being continued on the footprint 
side. We simply where not done with it with the v5 release but it was 
not bad enough to postpone the release.)



On 28/08/18 18:30, Wayne Stambaugh wrote:

I would be careful with any library improvements during stable bug fix
releases, particularly for symbol and 3d model libraries which are
linked rather than embedded.  My preference would be to just use the
same libraries tagged for the 5.0.0 release to keep changes to user
designs to a minimum.  Users can always download the latest libraries if
they prefer the bleeding edge.

On 8/28/2018 12:18 PM, Rene Pöschl wrote:

Is it planned to include a new version of the libraries as well?
Right now we ensure that the library is relatively stable so i think the
improvements made since the v5 release can easily be included.
(We do not allow major changes that would break backward compatibility.
My plan is to use this rule at least till after the 5.1 release. Maybe
even until the new file format is well enough implemented to play around
with it in the official library.)

On 27/08/18 21:38, Wayne Stambaugh wrote:

I would like to get the 5.0.1 release out by the end of September if at
all possible.  There are still a few open bug reports which need to be
fixed before we can release this so if you can fix any of the ones that
do not already have an assignee[1], any help would be appreciated.  My
goal is to have all of the bug reports closed by 9/15 and give the
package devs a few weeks before making the release announcement.

Cheers,

Wayne

[1]: https://launchpad.net/kicad/+milestone/5.0.1

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

I would be careful with any library improvements during stable bug fix
releases, particularly for symbol and 3d model libraries which are
linked rather than embedded.  My preference would be to just use the
same libraries tagged for the 5.0.0 release to keep changes to user
designs to a minimum.  Users can always download the latest libraries if
they prefer the bleeding edge.

On 8/28/2018 12:18 PM, Rene Pöschl wrote:
> Is it planned to include a new version of the libraries as well?
> Right now we ensure that the library is relatively stable so i think the
> improvements made since the v5 release can easily be included.
> (We do not allow major changes that would break backward compatibility.
> My plan is to use this rule at least till after the 5.1 release. Maybe
> even until the new file format is well enough implemented to play around
> with it in the official library.)
> 
> On 27/08/18 21:38, Wayne Stambaugh wrote:
>> I would like to get the 5.0.1 release out by the end of September if at
>> all possible.  There are still a few open bug reports which need to be
>> fixed before we can release this so if you can fix any of the ones that
>> do not already have an assignee[1], any help would be appreciated.  My
>> goal is to have all of the bug reports closed by 9/15 and give the
>> package devs a few weeks before making the release announcement.
>>
>> Cheers,
>>
>> Wayne
>>
>> [1]: https://launchpad.net/kicad/+milestone/5.0.1
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Rene Pöschl]

Is it planned to include a new version of the libraries as well?
Right now we ensure that the library is relatively stable so i think the 
improvements made since the v5 release can easily be included.
(We do not allow major changes that would break backward compatibility. 
My plan is to use this rule at least till after the 5.1 release. Maybe 
even until the new file format is well enough implemented to play around 
with it in the official library.)


On 27/08/18 21:38, Wayne Stambaugh wrote:

I would like to get the 5.0.1 release out by the end of September if at
all possible.  There are still a few open bug reports which need to be
fixed before we can release this so if you can fix any of the ones that
do not already have an assignee[1], any help would be appreciated.  My
goal is to have all of the bug reports closed by 9/15 and give the
package devs a few weeks before making the release announcement.

Cheers,

Wayne

[1]: https://launchpad.net/kicad/+milestone/5.0.1

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Adam Wolf]

Awesome, thanks! I explicitly turned it on for nightlies a few days after 5
came out, wanted to make sure I didn't need to explicitly turn it off.

Adam

On Mon, Aug 27, 2018, 2:53 PM Wayne Stambaugh  wrote:

> It's already enabled in the 5.0 branch so no extra steps should be
> required for the package developers.
>
> Wayne
>
> On 8/27/2018 3:41 PM, Adam Wolf wrote:
> > Beyond bug fixes, are we enabling the action menu stuff in the 5.0.1
> packages?
> >
> > Adam
> > On Mon, Aug 27, 2018 at 2:39 PM Wayne Stambaugh 
> wrote:
> >>
> >> I would like to get the 5.0.1 release out by the end of September if at
> >> all possible.  There are still a few open bug reports which need to be
> >> fixed before we can release this so if you can fix any of the ones that
> >> do not already have an assignee[1], any help would be appreciated.  My
> >> goal is to have all of the bug reports closed by 9/15 and give the
> >> package devs a few weeks before making the release announcement.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> [1]: https://launchpad.net/kicad/+milestone/5.0.1
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

It's already enabled in the 5.0 branch so no extra steps should be
required for the package developers.

Wayne

On 8/27/2018 3:41 PM, Adam Wolf wrote:
> Beyond bug fixes, are we enabling the action menu stuff in the 5.0.1 packages?
> 
> Adam
> On Mon, Aug 27, 2018 at 2:39 PM Wayne Stambaugh  wrote:
>>
>> I would like to get the 5.0.1 release out by the end of September if at
>> all possible.  There are still a few open bug reports which need to be
>> fixed before we can release this so if you can fix any of the ones that
>> do not already have an assignee[1], any help would be appreciated.  My
>> goal is to have all of the bug reports closed by 9/15 and give the
>> package devs a few weeks before making the release announcement.
>>
>> Cheers,
>>
>> Wayne
>>
>> [1]: https://launchpad.net/kicad/+milestone/5.0.1
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0.1 release

[Adam Wolf]

Beyond bug fixes, are we enabling the action menu stuff in the 5.0.1 packages?

Adam
On Mon, Aug 27, 2018 at 2:39 PM Wayne Stambaugh  wrote:
>
> I would like to get the 5.0.1 release out by the end of September if at
> all possible.  There are still a few open bug reports which need to be
> fixed before we can release this so if you can fix any of the ones that
> do not already have an assignee[1], any help would be appreciated.  My
> goal is to have all of the bug reports closed by 9/15 and give the
> package devs a few weeks before making the release announcement.
>
> Cheers,
>
> Wayne
>
> [1]: https://launchpad.net/kicad/+milestone/5.0.1
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.0.1 release

[Wayne Stambaugh]

I would like to get the 5.0.1 release out by the end of September if at
all possible.  There are still a few open bug reports which need to be
fixed before we can release this so if you can fix any of the ones that
do not already have an assignee[1], any help would be appreciated.  My
goal is to have all of the bug reports closed by 9/15 and give the
package devs a few weeks before making the release announcement.

Cheers,

Wayne

[1]: https://launchpad.net/kicad/+milestone/5.0.1

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp