Re: [Kicad-developers] 5.1.2 release announcement initial draft

2019-04-25 Thread Adam Wolf
5.1.2-1 for macOS is uploading on the slow Airbnb wifi. It may be a few hours yet, but it should be up soon! Adam On Wed, Apr 24, 2019 at 11:24 PM Wayne Stambaugh wrote: > > I believe they are in testing and ready to go. > > On 4/24/19 6:21 PM, Andrew Lutsenko wrote: > > Windows 5.1.2 builds ar

[Kicad-developers] Test failure since 5813164d1

2019-04-25 Thread Simon Richter
Hi, since 5813164d1 "SHAPE_ARC: fixed polyline conversion bug introduced in e312e2b286" we get test failures in the ArcToPolyline tests: [Error] - check chain.CPoint( 0 ) == c.m_geom.m_start_point has failed [[ 10 | 0 ] != [ -10 | 0 ]]Semicircle == [File] - /var/lib/jenkins/workspace/linux-kicad

[Kicad-developers] KiCon update.

2019-04-25 Thread Wayne Stambaugh
For those of you who are heading to KiCon and hoping to meet up with me before the meet up at Ballast Point Brewing, my flight has been delayed. I will not be arriving in Chicago until 4:15PM so I will be scrambling just to make the meet up. The joys of air travel :(. Cheers, Wayne __

Re: [Kicad-developers] Improving library editor checks

2019-04-25 Thread Wayne Stambaugh
Python scripting support is hopefully going to be implemented at some point during V6 development. This should allow you to integrate the KLC scripts directly into the symbol library editor. This will most likely happen late in V6 development because there are some major functional changes to the

Re: [Kicad-developers] CI builds

2019-04-25 Thread Simon Richter
Hi Nick, the main showstoppers are: 1. chroots On the old Jenkins, we just built on the host system, which meant the build environment was available instantly. The current system uses chroots, which have to be unpacked every time. Presumably this could be solved with Docker, where the unpacking

Re: [Kicad-developers] Improving library editor checks

2019-04-25 Thread Antonio Vázquez Blanco
>From the feedback given I am thinking about changing the proposal. Given that my ultimate goal was to integrate KLC check into KiCad to improve the quality of contributions and reduce librarian work, and that seems conflicting we may need to re-think my approach to the problem. I don't want to e

Re: [Kicad-developers] Improving library editor checks

2019-04-25 Thread Wayne Stambaugh
Antonio, Exactly what checks are you planning on implementing? As long as they are generic in nature like off grid pin checking, then I'm fine with that. If they are specific KLC checks like spacing, line width, etc, that is a different issue. We should not be forcing KLC rules on all users. I

Re: [Kicad-developers] CI builds

2019-04-25 Thread John Beard
On 24/04/2019 18:07, Adam Wolf wrote: I will set up a new view for the macbuilder that should be all green, and I can also set it up to push build failures to a list. Good idea. I did the same for Simon's Jenkins: https://jenkins.simonrichter.eu/view/KiCad%20Status Once you have such a view,

Re: [Kicad-developers] Improving library editor checks

2019-04-25 Thread John Beard
Hi Antonio, On 25/04/2019 10:39, Antonio Vázquez Blanco wrote: I've been playing around a little bit with KiCad source code lately and in the forums [1] I was encouraged to write to the dev mailing list in order to get feedback on how to improve the current library error checking. This looks

[Kicad-developers] Improving library editor checks

2019-04-25 Thread Antonio Vázquez Blanco
I've been playing around a little bit with KiCad source code lately and in the forums [1] I was encouraged to write to the dev mailing list in order to get feedback on how to improve the current library error checking. Summarizing the thread, I made some changes [2] so that a couple of KLC checks