kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

If ngspice-30 is completely broken on macos, we may have no choice but
to fall back to ngspice-26.  The brings the bugs that have been fixed
since ngspice-26 back into play which is less than ideal but I don't see
a solution unless there is a new release of ngspice that resolves the
issues.  We should try to work with Holger to try to resolve the issues
so we can provide a solution as soon as it's available.

Cheers,

Wayne

On 8/28/19 10:26 PM, Adam Wolf wrote:
> Jonathan, I hear you.  I rolled back to ngspice-26 for the 5.1.4
> release, and I think it probably makes sense to roll back to
> ngspice-26 for 5.1.5 as well.
> 
> I am not really comfortable with the state of this situation.  We're
> running nightlies with 30, and release with 26, but how long until
> there's a bug caused by rolling back for stable releases that we never
> see since all the nightlies are on ngspice-30?
> 
> Do I simply need to make another set of builds with ngspice-30 and a
> set with ngspice-26?  Is this fine? Maybe? Am I overthinking this?
> 
> Wayne, dev team, packagers, everyone--what do you think?  I don't have
> any skin in the game here.
> 
> Adam
> 
> On Wed, Aug 28, 2019 at 1:21 PM Jonatan Liljedahl <lijon@xxxxxxxxxxxx> wrote:
>>
>> It would be great if you could roll back to ngspice-26 in 5.1.5, at
>> least for macOS, since it seems completely broken (can't simulate
>> op-amps, etc).
>>
>> Cheers
>> /Jonatan
>>
>> On Wed, Aug 28, 2019 at 1:58 PM Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>>
>>> On 8/27/19 3:56 PM, Seth Hillbrand wrote:
>>>> Hi All-
>>>>
>>>> I know 5.1.4 is still in its infancy but I am hoping that we can plan
>>>> for a 5.1.5 during September (fixing at least 2 critical bugs).  We've
>>>> been a bit rocky with the point updates, so I'd like to propose a sequence:
>>>>
>>>> 1) Sometime around September 15: Tag 5.1.5-rc1 and announce string
>>>> freeze to give give translations a chance to update and tag 5.1.5
>>>> 2) At this point, we don't push anything to 5.1 unless it is fix for a
>>>> critical bug.  No other fixes until after 5.1.5.
>>>> 3) If there is a fix for a critical bug, we tag 5.1.5-rc2 after.
>>>> 4) 7 days after the last rc2 is tagged, we tag 5.1.5
>>>>
>>>> What do folks think about this scheme?  Maybe a way to avoid the 5.1.3
>>>> (and 5.1.1 and 5.0.1 before it) situation?
>>>>
>>>> -Seth
>>>
>>> Absolutely.  I was planning on this after the last debacle.  Hopefully
>>> the 5.1.5 release will go a bit more smoothly.
>>>
>>> Cheers,
>>>
>>> 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
>>
>>
>>
>> --
>> /Jonatan
>> http://kymatica.com
>>
>> _______________________________________________
>> 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
>