Re: [Kicad-developers] Stable version 4.0.5

2016-11-14 Thread Nick Østergaard
2016-11-14 20:18 GMT+01:00 Wayne Stambaugh : > On 11/14/2016 1:37 PM, Chris Pavlina wrote: >> On Sun, Nov 13, 2016 at 12:59:53PM -0500, Wayne Stambaugh wrote: >>> [snip] >>> Apparently package devs hate it because they >>> had remember to set the version and branch strings at

Re: [Kicad-developers] Stable version 4.0.5

2016-11-14 Thread Wayne Stambaugh
On 11/14/2016 1:37 PM, Chris Pavlina wrote: > On Sun, Nov 13, 2016 at 12:59:53PM -0500, Wayne Stambaugh wrote: >> [snip] >> Apparently package devs hate it because they >> had remember to set the version and branch strings at config time when >> building from source archives otherwise they end up

Re: [Kicad-developers] Stable version 4.0.5

2016-11-14 Thread Chris Pavlina
On Sun, Nov 13, 2016 at 12:59:53PM -0500, Wayne Stambaugh wrote: > [snip] > Apparently package devs hate it because they > had remember to set the version and branch strings at config time when > building from source archives otherwise they end up with no-vcs-found > version string. I see Chris

Re: [Kicad-developers] Stable version 4.0.5

2016-11-14 Thread Wayne Stambaugh
On 11/14/2016 3:45 AM, Nick Østergaard wrote: > Den 14/11/2016 00.02 skrev "Wayne Stambaugh" >: >> >> On 11/13/2016 1:47 PM, Nick Østergaard wrote: >> > 2016-11-13 19:29 GMT+01:00 Wayne Stambaugh

Re: [Kicad-developers] Stable version 4.0.5

2016-11-14 Thread Nick Østergaard
Den 14/11/2016 00.02 skrev "Wayne Stambaugh" : > > On 11/13/2016 1:47 PM, Nick Østergaard wrote: > > 2016-11-13 19:29 GMT+01:00 Wayne Stambaugh : > >> On 11/13/2016 1:15 PM, Nick Østergaard wrote: > >>> 2016-11-13 18:59 GMT+01:00 Wayne Stambaugh

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Wayne Stambaugh
On 11/13/2016 1:47 PM, Nick Østergaard wrote: > 2016-11-13 19:29 GMT+01:00 Wayne Stambaugh : >> On 11/13/2016 1:15 PM, Nick Østergaard wrote: >>> 2016-11-13 18:59 GMT+01:00 Wayne Stambaugh : Hey Nick, The problem with the boost 1.61 bug

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Nick Østergaard
2016-11-13 19:29 GMT+01:00 Wayne Stambaugh : > On 11/13/2016 1:15 PM, Nick Østergaard wrote: >> 2016-11-13 18:59 GMT+01:00 Wayne Stambaugh : >>> Hey Nick, >>> >>> The problem with the boost 1.61 bug fix in the master branch is that it >>> includes c++11

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Wayne Stambaugh
On 11/13/2016 1:15 PM, Nick Østergaard wrote: > 2016-11-13 18:59 GMT+01:00 Wayne Stambaugh : >> Hey Nick, >> >> The problem with the boost 1.61 bug fix in the master branch is that it >> includes c++11 code. That's why I didn't merge it into the stable >> branch. I want to

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Nick Østergaard
2016-11-13 18:59 GMT+01:00 Wayne Stambaugh : > Hey Nick, > > The problem with the boost 1.61 bug fix in the master branch is that it > includes c++11 code. That's why I didn't merge it into the stable > branch. I want to avoid c++11 in the stable 4 branch so we will have to

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Wayne Stambaugh
On 11/12/2016 2:15 PM, Michael Steinberg wrote: > Hi all, > >>> 1. Boost 1.61 compatibility and bugfix? >>> 2. Release version string. >>> >>> Should the release should include the boost 1.61 fix. It was >>> discussed in: >>> [Kicad-developers] About Bug 1604841: Pcbnew crash at moving via, and

Re: [Kicad-developers] Stable version 4.0.5

2016-11-13 Thread Wayne Stambaugh
Hey Nick, The problem with the boost 1.61 bug fix in the master branch is that it includes c++11 code. That's why I didn't merge it into the stable branch. I want to avoid c++11 in the stable 4 branch so we will have to let package devs know that they cannot build kicad against boost >= 1.61.

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Chris Pavlina
Should be fixed now. Wayne, both 7e3c025 and then b9c62b6 can go into stable. Please have a look at them too, I'm not really firing on all cylinders today and don't want to be 100% responsible for patches pushed directly to stable... On Sat, Nov 12, 2016 at 03:45:51PM -0500, Chris Pavlina wrote:

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Chris Pavlina
Quick update: yes, I just pushed a "fix" for this in 7e3c025, and yes, I realize it may not apply to stable. Apologies, I'm very busy and preoccupied this morning. Give me some time and I will prepare a patch that applies against stable. On Sat, Nov 12, 2016 at 05:55:16PM +0100, Nick Østergaard

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Nick Østergaard
2016-11-12 20:15 GMT+01:00 Michael Steinberg : > Hi all, > >>> 1. Boost 1.61 compatibility and bugfix? >>> 2. Release version string. >>> >>> Should the release should include the boost 1.61 fix. It was discussed >>> in: >>> [Kicad-developers] About Bug 1604841: Pcbnew crash

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Michael Steinberg
Hi all, 1. Boost 1.61 compatibility and bugfix? 2. Release version string. Should the release should include the boost 1.61 fix. It was discussed in: [Kicad-developers] About Bug 1604841: Pcbnew crash at moving via, and boost::context fixes to make it compatible with boost 1.61 And there is a

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Chris Pavlina
[2] may be my fault, I will have a look shortly. Not sure who ate [3]. On Sat, Nov 12, 2016 at 05:55:16PM +0100, Nick Østergaard wrote: > Hi Wayne, > > Good news to see a new release, but I wonder about two things: > > 1. Boost 1.61 compatibility and bugfix? > 2. Release version string. > >

Re: [Kicad-developers] Stable version 4.0.5

2016-11-12 Thread Nick Østergaard
Hi Wayne, Good news to see a new release, but I wonder about two things: 1. Boost 1.61 compatibility and bugfix? 2. Release version string. Should the release should include the boost 1.61 fix. It was discussed in: [Kicad-developers] About Bug 1604841: Pcbnew crash at moving via, and

[Kicad-developers] Stable version 4.0.5

2016-11-11 Thread Wayne Stambaugh
This is the last call for patches to the 4 stable branch. If I don't hear anything, I will set version string and tag 4.0.5 in the stable branch on Sunday and give our library, doc, translation, and package devs a couple of weeks to prepare before I make the official announcement. Thanks, Wayne