← Back to team overview

kicad-developers team mailing list archive

Re: V6 merge update


Hi Wayne,

I’d argue no, but it’s not black-and-white.  Everything will be backwards compatible with the proviso that if you enter a character in 6.0 that is excluded from 5.1 (say, “data:1”) and then read it in to 5.1, it will display escaped (“data{colon}1” in our example).

And if, for some strange reason, you had a label named “this{slash}that” in 5.1, 6.0 would display it as “this/that”.


> On 8 Mar 2019, at 20:29, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> Jeff,
> Wont this effectively change the schematic file format?  If so, then it
> will have to wait until the new schematic file format is implemented.  I
> don't want to make any changes to either that or the symbol file format
> so the legacy file format parsers can be frozen for all posterity once
> the file formats are implemented.
> Wayne
> On 2/21/2019 5:13 PM, Jeff Young wrote:
>> I just have the net-name-escaping stuff so that all characters can be used in labels, etc.
>> (Well, a couple of bug fixes too, but real minor stuff.)
>>> On 21 Feb 2019, at 13:21, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>> Since we are nearing the 5.1.0 release, I want to get an idea of what
>>> major merges are ready to go once 5.1 is branched.  I know Jon's netlist
>>> code is ready to merge and I'm pretty sure that should be the first big
>>> merge.  Does anyone else have any major changes they want to merge as
>>> soon as v6 starts?  I would like to get an idea of what changes to
>>> expect so we can avoid any serious merge chaos.  Please let me know what
>>> you have in the queue so I can get an idea of how we should proceed with
>>> the merges.
>>> TIA,
>>> Wayne
>>> _______________________________________________
>>> 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

Follow ups