kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 06/22/2018 12:29 PM, Adam Wolf wrote:
> I think this looks pretty good.
> 
> Is there somewhere we suggest people should go to ask for help?

The KiCad user forum is the best place to go for help.

> 
> What about adding a sentence near the beginning that says something
> like "Ideally, upgrading to a new version of KiCad would take no
> effort on your part.  We take effort to minimize changes that require
> special handling, but sometimes they are required in order to fix
> serious issues."
> 
> For upgrading users:
> 
> I will recommend that they should make a backup of their projects per
> this document.

There is a warning in the doc about backing up even though backups are
made by the remapping code.

> 
> Should I recommend for them to make a backup of their KiCad support
> directory (the one with template, library, et al)?

If you cannot install multiple version of KiCad on macos, than the user
would have to keep the v4 symbol libraries unless they didn't use them
in any of their schematics or they should use step 5 in the document.

> 
> Regarding fp-table-lib, should I recommend that users should make a
> backup of their current one?  Can I just tell them to move it to a
> backup, and will KiCad use a good one if there isn't a user-specific
> one?  Do I need to tell them to go into template/ and copy that one?

Not unless they want to copy the new default file and have customized
their global fp-lib-table.

> 
> Do I need to specify that users copy sym-table-lib out, or will KiCad
> do that automatically if they don't have one?

Eeschema will prompt the user the first time it's run and there is no
sym-lib-table file.  The default table contains all of the new symbol
libraries that are in the repo.

> 
> (I feel pretty guilty asking these questions but I think the
> alternative is that I dig into it and hold up the release :( )

No problem.  All of this is addressed in the doc so pointing this doc
would be an easy out.  It would also eliminate the need to keep things
synced should they change.

> 
> Adam
> On Fri, Jun 22, 2018 at 11:10 AM Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>
>> I pushed the v5 upgrade document to my personal repo[1] on git hub.  I
>> made it part of the KiCad documentation but I don't have a strong
>> opinion about where to add it.  This just seemed like the most logic
>> place.  Please review it when you get a chance.  If you find any issues
>> let me know, send me a patch, or submit a pull request against my doc
>> repo.  Keep in mind that this document is only to detail the changes
>> that will effect project compatibility with older versions of kicad and
>> the perils of symbol remapping.  Thanks in advance for the help.
>>
>> Cheers,
>>
>> Wayne
>>
>> [1]:
>> https://github.com/stambaughw/kicad-doc/blob/master/src/kicad/kicad_upgrading_from_v4_to_v5.adoc
>>
>> _______________________________________________
>> 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