kicad-developers team mailing list archive
Mailing list archive
Re: Footprint features - stable vs nightly
the only current thing in nightly not in stabel i know of is rounded
pads, this was added a few months ago, and there was a fair amount of
discussion on the list as how best to handle the non-backward
compatibility issues inherit with adding a feature like this. The
general concesus iirc was that no nightly-only footprints would be
merged into the github libs until kicad-5 is released.
I think for the current feature it might just be worth putting
something in a CI script that will be tested pre-merge into the github
libs and in the long term we can look at a better way for handling new
features in footprints/symbols/libs
On 11 March 2017 at 12:46, Chris Pavlina <pavlina.chris@xxxxxxxxx> wrote:
> This doesn't directly address your question - but couldn't the automated
> library checker actually load the footprints into KiCad, via the Python
> API, to truly verify that they parse in KiCad proper?
> On Sat, Mar 11, 2017 at 10:39:37AM +1100, Oliver Walters wrote:
>> Hi all,
>> Can someone tell me a complete list of the differences between footprint
>> "features" in nightly and stable? There is a recent issue where someone
>> added a footprint using roundrect pads and broke a library for someone
>> using stable.
>> I can easily add a search for "roundrect" to the automated library checker
>> but what else should I be looking for?
>> As an aside, I think it would be **very** helpful if the footprint library
>> loader was able to skip over "bad" footprints and continue to load.
>> Currently a single bad footprint prevents any subsequent footprints from
>> loading. If we had the ability to skip bad ones, then we could add "future"
>> footprints and these would simply be ignored by stable version.
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp