kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Hey Nick,

I just merged lp:kicad into the 4.0 branch and it's in the process of
building now.  If all goes well which it should, I'll tag it as rc2 and
commit it.  I'll also create a new archive and md5sum and upload them to
Launchpad.  Hopefully I'll get this done this evening.  If not, I'll
finish up some time tomorrow.

Wayne

On 11/8/2015 9:10 AM, Nick Østergaard wrote:
> Hi Wayne
> 
> Will we have an RC2 this weekend?
> 
> Since the issue reported by Andrew can not be reproduced by anyone
> anymore, I guess we can disreagard this.
> 
> But what about the warnings reported by Mark? I personally don't think
> theese should block RC2, they are afterall warnings, and there is
> still time to fix them before the stable release.
> 
> Nick
> 
> 2015-11-08 1:12 GMT+01:00 Andrew Zonenberg <azonenberg@xxxxxxxxxxxxxxx>:
>>
>> Confirmed to warn, but not crash, in r6302. Guess somebody fixed it
>> already.
>>
>> On 07/11/15 13:04, Wayne Stambaugh wrote:
>>> On 11/06/2015 12:25 PM, Andrew Zonenberg wrote:
>>>> There's another bug I spent a while hunting for earlier this
>>>> week, but couldn't get too far with. Maybe someone else can pick
>>>> it up?
>>>>
>>>> Steps to reproduce: * Open pad editor * Select pad type: SMT *
>>>> Select copper layers: none * Uncheck all technical layers
>>>>
>>>> In the debug build this will display a warning but keep running;
>>>> in release it aborts or crashes.
>>>>
>>>> Although *exiting* the pad editor should not be allowed if the
>>>> pad has no layers at all (or possibly pop up a dialog asking if
>>>> the user wants to delete it?), having no layers selected should
>>>> be a legal intermediate state during editing of a pad stack.
>>>
>>> I cannot even exit the pad properties dialog using the OK button.
>>> I keep getting an error message dialog "Error: no layer selected."
>>> every time I hit the OK button.  I'm using r6302 on Debian testing
>>> amd64 build.
>>>
>>>>
>>>> On 06/11/15 09:04, Mark Roszko wrote:
>>>>> One thing I didn't think was fixed yet was a null dereference
>>>>> introduced with the clipper library upgrade. jp fixed the
>>>>> uninitialized warnings but theres still a explicit null deref
>>>>> in a loop condition. CID 132144. What does it impact? No clue.
>>>>
>>>>> And speaking of pns, there is still CID 106401 where
>>>>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.