kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

Carl,

While I think that doing a little more git-fu is a good idea, I think that
KiCad needs a way to display news to users on startup across the board, so
we can tell users about new features and changes that may break their
boards regardless of where they are in the program.

I wrote this up in the first thread, and am finishing my reply there.

Adam Wolf
Cofounder and Engineer
Wayne and Layne

On Fri, Apr 24, 2015 at 9:32 PM, Carl Poirier <carl.poirier.2@xxxxxxxxx>
wrote:

> Jean-Paul, thanks for the first congratulations we get. Ricardo Crudo is
> the one who deserves it.
>
> Adam, I fully agree this can be better. I had suggested in the other
> thread to make a branch of each .pretty repository for each stable release.
> Then, the github plugin fetches that branch according to the software
> version. I don't think more branching/tagging than that is necessary once
> we have the first stable release.
>
> It shouldn't be too hard to implement either.
>
> Carl
>
> On Fri, Apr 24, 2015 at 10:21 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx
> > wrote:
>
>> Jean-Paul,
>>
>> I don't think anyone has complained on this list about the change
>> happening--neither I nor Garth have.  No one has proposed rolling it back.
>>
>> The complaint isn't that diodes now fit a standard--that's better than
>> before!
>>
>> The issue is that there is now mismatch between live footprints and
>> user's installed schematic symbols, and there isn't a good way to
>> communicate this to our users.  How many users follow the user mailing
>> list?  Under 1%?  Under 0.1%?  While posting on the users lists is
>> necessary, it is not sufficient!
>>
>> There are relatively simple technical solutions to communicate these
>> changes to users, and for some reason (certainly not for my blood pressure)
>> I'm volunteering to spend even more time on this project.
>>
>> Adam Wolf
>> Cofounder and Engineer
>> Wayne and Layne, LLC
>>
>> On Fri, Apr 24, 2015 at 9:02 PM, Jean-Paul Louis <louijp@xxxxxxxxx>
>> wrote:
>>
>>> Hi Adam,
>>>
>>> I do not see why the change in the library to make it compatible with
>>> other CAD packages, and IPC standards is a bad thing.
>>> Since the beginning, I always used my own library for diodes because
>>> they were broken in the KiCad library.
>>> At least now, I will be able to use the "standard” library.
>>>
>>> People who are complaining are just whiners. Everybody in the Pro world
>>> use pin 1 as the cathode of a diode. Our libraries were backward god knows
>>> why.
>>> We should thank the person who took the pain to fix it, instead of
>>> whining.
>>>
>>> Just my $0.02,
>>> Jean-Paul
>>> AC9GH
>>>
>>> > On Apr 24, 2015, at 9:01 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
>>> wrote:
>>> >
>>> > Hi folks,
>>> >
>>> > Git has tags and branches and a bunch of features to stop issues like
>>> this from happening.
>>> >
>>> > One easy way I think we can stop this from ever happening again:
>>> instead of always running off the newest commits to master, the github
>>> plugin could use a tag or a commit, and then when folks decide to update,
>>> we can parse and tell them what libraries changed and how, through metadata
>>> and commit messages, and they can choose when to update.
>>> >
>>> > This would stop changes in footprints from breaking users' boards due
>>> to static library files.
>>> >
>>> > Thoughts?
>>> >
>>> > Adam Wolf
>>> > Cofounder and Engineer
>>> > Wayne and Layne, LLC
>>> > _______________________________________________
>>> > 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
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>