kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

2015-07-28 21:11 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> On 7/28/2015 3:00 PM, Jon Neal wrote:
>> This is mostly to Wayne since he controls the releases.
>>
>> Now that the boost polygon code has been committed what is left for
>> kicad RC1? Any large roadblocks left?
>
> I have to look through the bug tracker to see if there are any more
> segfault and memory leak bug report and the latest Coverity scan to see
> if there are any remaining errors with high severity that need to be
> addressed.  Once this number goes to 0, then we can start thinking about
> a stable release candidate.

For what I can see there are only two bugs left tagged as high, where
one of them is a potential duplicate of another bugs which was marked
as fix committed. And the other one is "just" an asssert.

There are some other segfaults reported, but the reporters have not
provided enough information to really describe the bug properly.

>>
>> Also, several people in IRC have been talking and are really hoping that
>> the release candidates will be debug builds to help fix bugs faster. Any
>> chance of that happening?
>
> This depends on our package developers.  I'm all for debug builds if it
> will help to speed along the debugging.  I think Adam is providing
> nightly debug builds for OSX.  The other platform package developers
> feel free to chime in here.
>
> All of this being said, I think we are getting close.  I'm going to try
> to put together a list of action items that need to be addressed for a
> stable release candidate.  Hopefully I can get to that this weekend.

I am packaging the windows builds, but I have not yet made it run
smooth on Jenkins yet, so I am still building them manually once in a
while. I tried to make a debug build, but I did not have enough space
left on my device. This is the reason for there being no windows
builds configured as debug yet.

I am definitely for nightlies are debug builds.