Re: [Kicad-developers] 5.1.3 release

[Nick Østergaard]

kicad-doc 5.1.4 has been tagged

Windows builds should be up in an hour or two.

On Wed, 7 Aug 2019 at 18:23, Nick Østergaard  wrote:
>
> Yes. There is an issue on the 5.1.3 of kicad-doc that and we need to include 
> the fix for that in 5.1.4 and test it.
>
> ons. 7. aug. 2019 17.44 skrev Wayne Stambaugh :
>>
>>
>>
>> On 8/7/19 9:33 AM, Steven A. Falco wrote:
>> > On 8/5/19 9:35 AM, Steven A. Falco wrote:
>> >> On 8/4/19 6:02 PM, Rene Pöschl wrote:
>> >>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
>>  Please tag the doc, translation,
>>  and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
>>  the release announcement and there will be no official 5.1.3 release.
>>  Thank you everyone for your cooperation and patience.
>> 
>>  Cheers,
>> 
>>  Wayne
>> >>>
>> >>>
>> >>> The library is tagged
>> >>
>> >> Good - as soon as doc and i18n get tagged I'll start a Fedora build.
>> >>
>> >
>> > Still waiting for doc and i18n to be tagged.  Someone please tag them so I 
>> > can start a 5.1.4 build.
>> >
>> >   Thanks,
>> >   Steve
>> >
>>
>> Is there any reason why we haven't tagged the doc and i18n repos yet?
>> The 5.1.4 tag should be the same commit as 5.1.3.  I can do it if the
>> need be.
>>
>> 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.1.3 release

[Nick Østergaard]

Yes. There is an issue on the 5.1.3 of kicad-doc that and we need to
include the fix for that in 5.1.4 and test it.

ons. 7. aug. 2019 17.44 skrev Wayne Stambaugh :

>
>
> On 8/7/19 9:33 AM, Steven A. Falco wrote:
> > On 8/5/19 9:35 AM, Steven A. Falco wrote:
> >> On 8/4/19 6:02 PM, Rene Pöschl wrote:
> >>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
>  Please tag the doc, translation,
>  and library repos to 5.1.4 using the same commit as 5.1.3.  I'll
> update
>  the release announcement and there will be no official 5.1.3 release.
>  Thank you everyone for your cooperation and patience.
> 
>  Cheers,
> 
>  Wayne
> >>>
> >>>
> >>> The library is tagged
> >>
> >> Good - as soon as doc and i18n get tagged I'll start a Fedora build.
> >>
> >
> > Still waiting for doc and i18n to be tagged.  Someone please tag them so
> I can start a 5.1.4 build.
> >
> >   Thanks,
> >   Steve
> >
>
> Is there any reason why we haven't tagged the doc and i18n repos yet?
> The 5.1.4 tag should be the same commit as 5.1.3.  I can do it if the
> need be.
>
> 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.1.3 release

[Wayne Stambaugh]

On 8/7/19 9:33 AM, Steven A. Falco wrote:
> On 8/5/19 9:35 AM, Steven A. Falco wrote:
>> On 8/4/19 6:02 PM, Rene Pöschl wrote:
>>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
 Please tag the doc, translation,
 and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
 the release announcement and there will be no official 5.1.3 release.
 Thank you everyone for your cooperation and patience.

 Cheers,

 Wayne
>>>
>>>
>>> The library is tagged
>>
>> Good - as soon as doc and i18n get tagged I'll start a Fedora build.
>>
> 
> Still waiting for doc and i18n to be tagged.  Someone please tag them so I 
> can start a 5.1.4 build.
> 
>   Thanks,
>   Steve
> 

Is there any reason why we haven't tagged the doc and i18n repos yet?
The 5.1.4 tag should be the same commit as 5.1.3.  I can do it if the
need be.

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.1.3 release

[Steven A. Falco]

On 8/5/19 9:35 AM, Steven A. Falco wrote:
> On 8/4/19 6:02 PM, Rene Pöschl wrote:
>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
>>> Please tag the doc, translation,
>>> and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
>>> the release announcement and there will be no official 5.1.3 release.
>>> Thank you everyone for your cooperation and patience.
>>>
>>> Cheers,
>>>
>>> Wayne
>>
>>
>> The library is tagged
> 
> Good - as soon as doc and i18n get tagged I'll start a Fedora build.
> 

Still waiting for doc and i18n to be tagged.  Someone please tag them so I can 
start a 5.1.4 build.

Thanks,
Steve


___
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.1.3 release

[Frank Severinsen]

Hi Eeli

Jeff disabled it during this fix: 


It's reenabled in nightlies, but I'm not sure if the router improvements are 
too big to put in V5.1 branch

Den 5. august 2019 kl. 15.42.16 +02.00, skrev Eeli Kaikkonen 
:

> 
> 
> 
> ma 5. elok. 2019 klo 16.02 Eeli Kaikkonen () 
> kirjoitti:
> 
> > A very quick notice and maybe alert. I just tried 5.1.4-4-g450dac4b1from 
> > Windows testing downloads. I can't drag vias with D. I will test further. 
> > It it's really a bug it may affect 5.1.4.
> > 
> > 
> I'm not sure what this is, but here's a screencast. What I do:
> 1. Press D on a via which is attached to tracks. Nothing seems to happen 
> until the cursor reaches a point where the via can be moved. Before that it 
> looks like non-functioning.
> 2. Press D on a stitching via. It doesn't move and nothing happens. 
> (Previously it was moved, although there was a bug which let it be placed to 
> violated DRC. So, maybe this is on purpose?)
> 3. Press G on a stiching via. It moves. Very good.
> 
> Because none of them was moved when I tried quickly with D I thought there's 
> some problem.
> 
> Ubtp0AruRO.mp4 
> 
> 
> Eeli Kaikkonen
> 
> 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
> 

___
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.1.3 release

[Eeli Kaikkonen]

ma 5. elok. 2019 klo 16.02 Eeli Kaikkonen (eeli.kaikko...@gmail.com)
kirjoitti:

> A very quick notice and maybe alert. I just tried 5.1.4-4-g450dac4b1from
> Windows testing downloads. I can't drag vias with D. I will test further.
> It it's really a bug it may affect 5.1.4.
>
>
I'm not sure what this is, but here's a screencast. What I do:
1. Press D on a via which is attached to tracks. Nothing seems to happen
until the cursor reaches a point where the via can be moved. Before that it
looks like non-functioning.
2. Press D on a stitching via. It doesn't move and nothing happens.
(Previously it was moved, although there was a bug which let it be placed
to violated DRC. So, maybe this is on purpose?)
3. Press G on a stiching via. It moves. Very good.

Because none of them was moved when I tried quickly with D I thought
there's some problem.
 Ubtp0AruRO.mp4


Eeli Kaikkonen
___
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.1.3 release

[Steven A. Falco]

On 8/4/19 6:02 PM, Rene Pöschl wrote:
> On 04/08/2019 19:03, Wayne Stambaugh wrote:
>> Please tag the doc, translation,
>> and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
>> the release announcement and there will be no official 5.1.3 release.
>> Thank you everyone for your cooperation and patience.
>>
>> Cheers,
>>
>> Wayne
> 
> 
> The library is tagged

Good - as soon as doc and i18n get tagged I'll start a Fedora build.

Steve

___
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.1.3 release

[Eeli Kaikkonen]

su 4. elok. 2019 klo 20.03 Wayne Stambaugh (stambau...@gmail.com) kirjoitti:

>
> I decided to revert all of the commits that contained UI string changes
> and tagged 5.1.4.  It's ugly but it contains the Fedora fix along with
> the update footprint position fix.  I already uploaded the source
> archive and started a 5.1.5 milestone.  Please tag the doc, translation,
> and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
> the release announcement and there will be no official 5.1.3 release.
> Thank you everyone for your cooperation and patience.
>

A very quick notice and maybe alert. I just tried 5.1.4-4-g450dac4b1from
Windows testing downloads. I can't drag vias with D. I will test further.
It it's really a bug it may affect 5.1.4.

Eeli Kaikkonen
___
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.1.3 release

[Rene Pöschl]

On 04/08/2019 19:03, Wayne Stambaugh wrote:

Please tag the doc, translation,
and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
the release announcement and there will be no official 5.1.3 release.
Thank you everyone for your cooperation and patience.

Cheers,

Wayne



The library is tagged


___
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.1.3 release

[Wayne Stambaugh]

On 8/4/19 11:07 AM, Steven A. Falco wrote:
> On 8/3/19 1:00 PM, Seth Hillbrand wrote:
>> On 2019-08-03 11:12, Wayne Stambaugh wrote:
>>> On 8/2/19 5:18 PM, Steven A. Falco wrote:
 On 8/2/19 3:05 PM, Wayne Stambaugh wrote:
> Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
> This bug is a definite show stopper.  We need to do a better job of
> testing fixes before we merge them into the 5.1 branch.  Maybe we need
> to start doing release candidates on the stable branch before releasing
> buggy bug fixes?  For those packagers who are providing 5.1.3 for
> distos, I would avoid releasing it.

 I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a Fedora 
 admin to grant me additional privileges to do so, since the build has 
 already entered the package queue.

 I'll wait for 5.1.4 to be tagged and then I'll start up a new build.

 As to Wayne having to delay his announcement because of insufficient 
 Fedora karma, I'll request that people on this list test and give karma 
 for future builds.  Just three positive votes will be sufficient to 
 expedite release.

 As to the discussion from https://bugs.launchpad.net/kicad/+bug/1838448 
 I've now had two folks working for RedHat advise me not to circumvent the 
 _GLIBCXX_ASSERTIONS, because of security concerns related to buffer 
 overflows.  So I think in the interest of safety, I need to leave those 
 asserts in place.

 Steve

>>>
>>> I think I found a solution.  I can tag commit
>>> 090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.  No translations are
>>> required so we should be able to tag the translations, libs, and docs at
>>> the same commit as the 5.1.3 tag.  This would only require updating the
>>> builds and stable release announcement.  Unfortunately this doesn't
>>> solve the assertion issue on Fedora.  If I include the commits that fix
>>> the Fedora issue, we will have to wait for the translations because
>>> there are a bunch of string changes after commit
>>> cf949609b25a43b66b985baab8ae5354ad8510ae so including them would push
>>> back the release significantly.  If there are no objections, I will tag
>>> 5.1.4 today so we can get moving on a new stable release.
>>>
>>> Cheers,
>>>
>>> Wayne
>>
>> Hi Wayne-
>>
>> We could revert the commits post 090073cc3b79f4f646f3c82390eb02a253e488d8 
>> that changed strings and then tag 5.1.4 and re-commit the reverts.  Not 
>> pretty but it for a one-off, it might not be so bad.
>>
>> -Seth
> 
> Wayne - have you decided to tag 090073cc3b79f4f646f3c82390eb02a253e488d8 as 
> 5.1.4 or follow Seth's approach?
> 
> I was able to stop 5.1.3 from being released in Fedora 30, but I was _not_ 
> able to stop it from being released in Fedora Rawhide.
> 
> If 5.1.4 will be tagged soon, then that will fix Rawhide.  If 5.1.4 will be 
> delayed significantly, then I will probably need to do something semi-ugly 
> (involving a permanent Epoch change) in order to force Rawhide to downgrade 
> to 5.1.2.  How critical is the bug that was found in 5.1.3?
> 
>   Steve
> 

I decided to revert all of the commits that contained UI string changes
and tagged 5.1.4.  It's ugly but it contains the Fedora fix along with
the update footprint position fix.  I already uploaded the source
archive and started a 5.1.5 milestone.  Please tag the doc, translation,
and library repos to 5.1.4 using the same commit as 5.1.3.  I'll update
the release announcement and there will be no official 5.1.3 release.
Thank you everyone for your cooperation and patience.

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.1.3 release

[Steven A. Falco]

On 8/3/19 1:00 PM, Seth Hillbrand wrote:
> On 2019-08-03 11:12, Wayne Stambaugh wrote:
>> On 8/2/19 5:18 PM, Steven A. Falco wrote:
>>> On 8/2/19 3:05 PM, Wayne Stambaugh wrote:
 Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
 This bug is a definite show stopper.  We need to do a better job of
 testing fixes before we merge them into the 5.1 branch.  Maybe we need
 to start doing release candidates on the stable branch before releasing
 buggy bug fixes?  For those packagers who are providing 5.1.3 for
 distos, I would avoid releasing it.
>>>
>>> I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a Fedora 
>>> admin to grant me additional privileges to do so, since the build has 
>>> already entered the package queue.
>>>
>>> I'll wait for 5.1.4 to be tagged and then I'll start up a new build.
>>>
>>> As to Wayne having to delay his announcement because of insufficient Fedora 
>>> karma, I'll request that people on this list test and give karma for future 
>>> builds.  Just three positive votes will be sufficient to expedite release.
>>>
>>> As to the discussion from https://bugs.launchpad.net/kicad/+bug/1838448 
>>> I've now had two folks working for RedHat advise me not to circumvent the 
>>> _GLIBCXX_ASSERTIONS, because of security concerns related to buffer 
>>> overflows.  So I think in the interest of safety, I need to leave those 
>>> asserts in place.
>>>
>>> Steve
>>>
>>
>> I think I found a solution.  I can tag commit
>> 090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.  No translations are
>> required so we should be able to tag the translations, libs, and docs at
>> the same commit as the 5.1.3 tag.  This would only require updating the
>> builds and stable release announcement.  Unfortunately this doesn't
>> solve the assertion issue on Fedora.  If I include the commits that fix
>> the Fedora issue, we will have to wait for the translations because
>> there are a bunch of string changes after commit
>> cf949609b25a43b66b985baab8ae5354ad8510ae so including them would push
>> back the release significantly.  If there are no objections, I will tag
>> 5.1.4 today so we can get moving on a new stable release.
>>
>> Cheers,
>>
>> Wayne
> 
> Hi Wayne-
> 
> We could revert the commits post 090073cc3b79f4f646f3c82390eb02a253e488d8 
> that changed strings and then tag 5.1.4 and re-commit the reverts.  Not 
> pretty but it for a one-off, it might not be so bad.
> 
> -Seth

Wayne - have you decided to tag 090073cc3b79f4f646f3c82390eb02a253e488d8 as 
5.1.4 or follow Seth's approach?

I was able to stop 5.1.3 from being released in Fedora 30, but I was _not_ able 
to stop it from being released in Fedora Rawhide.

If 5.1.4 will be tagged soon, then that will fix Rawhide.  If 5.1.4 will be 
delayed significantly, then I will probably need to do something semi-ugly 
(involving a permanent Epoch change) in order to force Rawhide to downgrade to 
5.1.2.  How critical is the bug that was found in 5.1.3?

Steve


___
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.1.3 release

[Seth Hillbrand]

On 2019-08-03 11:12, Wayne Stambaugh wrote:

On 8/2/19 5:18 PM, Steven A. Falco wrote:

On 8/2/19 3:05 PM, Wayne Stambaugh wrote:

Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
This bug is a definite show stopper.  We need to do a better job of
testing fixes before we merge them into the 5.1 branch.  Maybe we 
need
to start doing release candidates on the stable branch before 
releasing

buggy bug fixes?  For those packagers who are providing 5.1.3 for
distos, I would avoid releasing it.


I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a 
Fedora admin to grant me additional privileges to do so, since the 
build has already entered the package queue.


I'll wait for 5.1.4 to be tagged and then I'll start up a new build.

As to Wayne having to delay his announcement because of insufficient 
Fedora karma, I'll request that people on this list test and give 
karma for future builds.  Just three positive votes will be sufficient 
to expedite release.


As to the discussion from 
https://bugs.launchpad.net/kicad/+bug/1838448 I've now had two folks 
working for RedHat advise me not to circumvent the 
_GLIBCXX_ASSERTIONS, because of security concerns related to buffer 
overflows.  So I think in the interest of safety, I need to leave 
those asserts in place.


Steve



I think I found a solution.  I can tag commit
090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.  No translations are
required so we should be able to tag the translations, libs, and docs 
at

the same commit as the 5.1.3 tag.  This would only require updating the
builds and stable release announcement.  Unfortunately this doesn't
solve the assertion issue on Fedora.  If I include the commits that fix
the Fedora issue, we will have to wait for the translations because
there are a bunch of string changes after commit
cf949609b25a43b66b985baab8ae5354ad8510ae so including them would push
back the release significantly.  If there are no objections, I will tag
5.1.4 today so we can get moving on a new stable release.

Cheers,

Wayne


Hi Wayne-

We could revert the commits post 
090073cc3b79f4f646f3c82390eb02a253e488d8 that changed strings and then 
tag 5.1.4 and re-commit the reverts.  Not pretty but it for a one-off, 
it might not be so bad.


-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.1.3 release

[Steven A. Falco]

On 8/3/19 11:12 AM, Wayne Stambaugh wrote:
> 
> On 8/2/19 5:18 PM, Steven A. Falco wrote:
>> On 8/2/19 3:05 PM, Wayne Stambaugh wrote:
>>> Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
>>> This bug is a definite show stopper.  We need to do a better job of
>>> testing fixes before we merge them into the 5.1 branch.  Maybe we need
>>> to start doing release candidates on the stable branch before releasing
>>> buggy bug fixes?  For those packagers who are providing 5.1.3 for
>>> distos, I would avoid releasing it.
>>
>> I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a Fedora 
>> admin to grant me additional privileges to do so, since the build has 
>> already entered the package queue.
>>
>> I'll wait for 5.1.4 to be tagged and then I'll start up a new build.
>>
>> As to Wayne having to delay his announcement because of insufficient Fedora 
>> karma, I'll request that people on this list test and give karma for future 
>> builds.  Just three positive votes will be sufficient to expedite release.
>>
>> As to the discussion from https://bugs.launchpad.net/kicad/+bug/1838448 I've 
>> now had two folks working for RedHat advise me not to circumvent the 
>> _GLIBCXX_ASSERTIONS, because of security concerns related to buffer 
>> overflows.  So I think in the interest of safety, I need to leave those 
>> asserts in place.
>>
>>  Steve
>>
> 
> I think I found a solution.  I can tag commit
> 090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.  No translations are
> required so we should be able to tag the translations, libs, and docs at
> the same commit as the 5.1.3 tag.  This would only require updating the
> builds and stable release announcement.  Unfortunately this doesn't
> solve the assertion issue on Fedora.  If I include the commits that fix
> the Fedora issue, we will have to wait for the translations because
> there are a bunch of string changes after commit
> cf949609b25a43b66b985baab8ae5354ad8510ae so including them would push
> back the release significantly.  If there are no objections, I will tag
> 5.1.4 today so we can get moving on a new stable release.
> 
> Cheers,
> 
> Wayne

I'm fine with tagging 090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.

Steve


___
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.1.3 release

[Wayne Stambaugh]

On 8/2/19 5:18 PM, Steven A. Falco wrote:
> On 8/2/19 3:05 PM, Wayne Stambaugh wrote:
>> Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
>> This bug is a definite show stopper.  We need to do a better job of
>> testing fixes before we merge them into the 5.1 branch.  Maybe we need
>> to start doing release candidates on the stable branch before releasing
>> buggy bug fixes?  For those packagers who are providing 5.1.3 for
>> distos, I would avoid releasing it.
> 
> I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a Fedora 
> admin to grant me additional privileges to do so, since the build has already 
> entered the package queue.
> 
> I'll wait for 5.1.4 to be tagged and then I'll start up a new build.
> 
> As to Wayne having to delay his announcement because of insufficient Fedora 
> karma, I'll request that people on this list test and give karma for future 
> builds.  Just three positive votes will be sufficient to expedite release.
> 
> As to the discussion from https://bugs.launchpad.net/kicad/+bug/1838448 I've 
> now had two folks working for RedHat advise me not to circumvent the 
> _GLIBCXX_ASSERTIONS, because of security concerns related to buffer 
> overflows.  So I think in the interest of safety, I need to leave those 
> asserts in place.
> 
>   Steve
> 

I think I found a solution.  I can tag commit
090073cc3b79f4f646f3c82390eb02a253e488d8 as 5.1.4.  No translations are
required so we should be able to tag the translations, libs, and docs at
the same commit as the 5.1.3 tag.  This would only require updating the
builds and stable release announcement.  Unfortunately this doesn't
solve the assertion issue on Fedora.  If I include the commits that fix
the Fedora issue, we will have to wait for the translations because
there are a bunch of string changes after commit
cf949609b25a43b66b985baab8ae5354ad8510ae so including them would push
back the release significantly.  If there are no objections, I will tag
5.1.4 today so we can get moving on a new stable release.

Cheers,

Wayne

[1]:
https://git.launchpad.net/kicad/commit/?h=5.1=090073cc3b79f4f646f3c82390eb02a253e488d8
[2]:
https://git.launchpad.net/kicad/commit/?h=5.1=cf949609b25a43b66b985baab8ae5354ad8510ae

___
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.1.3 release

[Steven A. Falco]

On 8/2/19 3:05 PM, Wayne Stambaugh wrote:
> Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
> This bug is a definite show stopper.  We need to do a better job of
> testing fixes before we merge them into the 5.1 branch.  Maybe we need
> to start doing release candidates on the stable branch before releasing
> buggy bug fixes?  For those packagers who are providing 5.1.3 for
> distos, I would avoid releasing it.

I'm attempting to stop 5.1.3 from moving into Fedora.  I may need a Fedora 
admin to grant me additional privileges to do so, since the build has already 
entered the package queue.

I'll wait for 5.1.4 to be tagged and then I'll start up a new build.

As to Wayne having to delay his announcement because of insufficient Fedora 
karma, I'll request that people on this list test and give karma for future 
builds.  Just three positive votes will be sufficient to expedite release.

As to the discussion from https://bugs.launchpad.net/kicad/+bug/1838448 I've 
now had two folks working for RedHat advise me not to circumvent the 
_GLIBCXX_ASSERTIONS, because of security concerns related to buffer overflows.  
So I think in the interest of safety, I need to leave those asserts in place.

Steve

___
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.1.3 release

[Eeli Kaikkonen]

pe 2. elok. 2019 klo 22.39 Wayne Stambaugh (stambau...@gmail.com) kirjoitti:

> I'm not proposing moving a tag.  I am only proposing that 5.1.3 never
> gets released.  We just go from 5.1.2 to 5.1.4.  This shouldn't cause
> any issues.
>

I understood that. I read your post just after sending mine. Sorry for the
noise :)

About possible RCs. In the user forum we have been busy linking to the 5.1
testing builds and telling that they are pretty stable. The links have been
pretty popular. I'm not sure tagging RCs would give you much more testing.
Maybe a week or so without commits before tagging a release would help, in
that case the last commit before the release could be called RC and
announced. That would probably gather a bit larger user base. But this is
just me guessing.

Eeli Kaikkonen
___
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.1.3 release

[Jeff Young]

The release candidates would be a good idea if we think anyone would test them. 
  The failure mode would be if all those willing to take the risk were only 
willing to take it in order to see the next major version (ie: were running the 
master nightlies).

Another option would be to only back-port critical (and perhaps high) priority 
bugs to the dot-release branches….


> On 2 Aug 2019, at 13:05, Wayne Stambaugh  wrote:
> 
> Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
> This bug is a definite show stopper.  We need to do a better job of
> testing fixes before we merge them into the 5.1 branch.  Maybe we need
> to start doing release candidates on the stable branch before releasing
> buggy bug fixes?  For those packagers who are providing 5.1.3 for
> distos, I would avoid releasing it.
> 
> Cheers,
> 
> Wayne
> 
> 
> On 8/2/19 2:33 PM, jp charras wrote:
>> Hi Wayne,
>> 
>> If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very
>> annoying bug:
>> Bug #1838446
>> 
>> This bug was fixed the Jul 31.
>> 
>> This bug make impossible updating footprints, both from the dialog and
>> from schematic, because the new footprint is not at the right place (the
>> old footprint coordinate) but it is placed at the mouse cursor location.
>> 
>> 
> 
> ___
> 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.1.3 release

[Wayne Stambaugh]

On 8/2/19 3:06 PM, Eeli Kaikkonen wrote:
> pe 2. elok. 2019 klo 21.33 jp charras (jp.char...@wanadoo.fr
> ) kirjoitti:
> 
> If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very
> annoying bug:
> Bug #1838446
> 
> This bug was fixed the Jul 31.
> 
> This bug make impossible updating footprints, both from the dialog and
> from schematic, because the new footprint is not at the right place (the
> old footprint coordinate) but it is placed at the mouse cursor location.
> 
> 
> Numbers are cheap, so why not announce 5.1.3, tell that it will have
> short life and tag 5.1.4 immediately (or as soon as possible)? Moving an
> existing tag and building new packages would lead to a mess.
> 
> Eeli Kaikkonen

I'm not proposing moving a tag.  I am only proposing that 5.1.3 never
gets released.  We just go from 5.1.2 to 5.1.4.  This shouldn't cause
any issues.

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.1.3 release

[Eeli Kaikkonen]

pe 2. elok. 2019 klo 21.33 jp charras (jp.char...@wanadoo.fr) kirjoitti:

> If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very
> annoying bug:
> Bug #1838446
>
> This bug was fixed the Jul 31.
>
> This bug make impossible updating footprints, both from the dialog and
> from schematic, because the new footprint is not at the right place (the
> old footprint coordinate) but it is placed at the mouse cursor location.
>

Numbers are cheap, so why not announce 5.1.3, tell that it will have short
life and tag 5.1.4 immediately (or as soon as possible)? Moving an existing
tag and building new packages would lead to a mess.

Eeli Kaikkonen
___
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.1.3 release

[Wayne Stambaugh]

Looks like we will be forgoing a 5.1.3 release and jumping to 5.1.4.
This bug is a definite show stopper.  We need to do a better job of
testing fixes before we merge them into the 5.1 branch.  Maybe we need
to start doing release candidates on the stable branch before releasing
buggy bug fixes?  For those packagers who are providing 5.1.3 for
distos, I would avoid releasing it.

Cheers,

Wayne


On 8/2/19 2:33 PM, jp charras wrote:
> Hi Wayne,
> 
> If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very
> annoying bug:
> Bug #1838446
> 
> This bug was fixed the Jul 31.
> 
> This bug make impossible updating footprints, both from the dialog and
> from schematic, because the new footprint is not at the right place (the
> old footprint coordinate) but it is placed at the mouse cursor location.
> 
> 

___
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.1.3 release

[jp charras]

Hi Wayne,

If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very
annoying bug:
Bug #1838446

This bug was fixed the Jul 31.

This bug make impossible updating footprints, both from the dialog and
from schematic, because the new footprint is not at the right place (the
old footprint coordinate) but it is placed at the mouse cursor location.


-- 
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.1.3 release

[Wayne Stambaugh]

Seeing that Fedora is one of the major distros, I will push the release
announcement to a week from today.  Thanks for the update.

Cheers,

Wayne


On 8/2/2019 11:13 AM, Steven A. Falco wrote:
> The Fedora build of 5.1.3 is waiting for Karma.  It will be available in 
> about 6 days.  I have another build in the pipeline owing to bug 1838448, 
> which should become available a few days later.
> 
>   Steve
> 
> On 8/2/19 11:07 AM, Wayne Stambaugh wrote:
>> Where do we stand on packaging for the 5.1.3 stable release?  We should
>> be close but I didn't see the updates to the website download links.  I
>> would like to make the release announcement tomorrow or Sunday if
>> possible.  Please let me know if this and issue.
>>
>> 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.1.3 release

[Adam Wolf]

MacOS would be ready today.  I'll upload packages and prep a PR (not to
merge until everything is loaded).

On Fri, Aug 2, 2019, 10:36 AM Wayne Stambaugh  wrote:

> Seeing that Fedora is one of the major distros, I will push the release
> announcement to a week from today.  Thanks for the update.
>
> Cheers,
>
> Wayne
>
>
> On 8/2/2019 11:13 AM, Steven A. Falco wrote:
> > The Fedora build of 5.1.3 is waiting for Karma.  It will be available in
> about 6 days.  I have another build in the pipeline owing to bug 1838448,
> which should become available a few days later.
> >
> >   Steve
> >
> > On 8/2/19 11:07 AM, Wayne Stambaugh wrote:
> >> Where do we stand on packaging for the 5.1.3 stable release?  We should
> >> be close but I didn't see the updates to the website download links.  I
> >> would like to make the release announcement tomorrow or Sunday if
> >> possible.  Please let me know if this and issue.
> >>
> >> 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.1.3 release

[Jean-Samuel Reynaud]

For Ubuntu packages (ppa) it's ok everything is built since few days.

Regards

Le ven. 2 août 2019 à 17:08, Wayne Stambaugh  a
écrit :

> Where do we stand on packaging for the 5.1.3 stable release?  We should
> be close but I didn't see the updates to the website download links.  I
> would like to make the release announcement tomorrow or Sunday if
> possible.  Please let me know if this and issue.
>
> 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.1.3 release

[Steven A. Falco]

The Fedora build of 5.1.3 is waiting for Karma.  It will be available in about 
6 days.  I have another build in the pipeline owing to bug 1838448, which 
should become available a few days later.

Steve

On 8/2/19 11:07 AM, Wayne Stambaugh wrote:
> Where do we stand on packaging for the 5.1.3 stable release?  We should
> be close but I didn't see the updates to the website download links.  I
> would like to make the release announcement tomorrow or Sunday if
> possible.  Please let me know if this and issue.
> 
> 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