Re: [Emc-developers] New Trajectory Planner

2014-04-01 Thread Marius Liebenberg
What was the verdict then, is this work going to be incorporated somewhere in the near future or will we have to wait until Robert has done more to it? On 2014-03-21 20:55, John Thornton wrote: > I have a friend that is very interested in the new trajectory planner > with an X, Z, A machine. Is

Re: [Emc-developers] New Trajectory Planner

2014-04-01 Thread Sebastian Kuzminsky
On 4/1/14 14:27 , Marius Liebenberg wrote: > What was the verdict then, is this work going to be incorporated > somewhere in the near future or will we have to wait until Robert has > done more to it? I'm not sure exactly what state it's in currently. After i make the 2.6 branch I hope to speak

Re: [Emc-developers] New Trajectory Planner

2014-04-01 Thread sam sokolik
This is what I was expecting also... (big changes needs a lot of testing before release) (and this was started during the 2.6 work...) sam On 04/01/2014 03:45 PM, Sebastian Kuzminsky wrote: > On 4/1/14 14:27 , Marius Liebenberg wrote: >> What was the verdict then, is this work going to be inc

[Emc-developers] 2.6 status?

2014-04-01 Thread David Bagby
Hi Seb, On 4/1/2014 1:45 PM, Sebastian Kuzminsky wrote: > I'm not sure exactly what state it's in currently. After i make the > 2.6 branch I hope to speak with Sam Sokolik and Robert Ellenberg and > see where things stand. I'm hoping to merge it into master for the > following (2.7) release cyc

Re: [Emc-developers] New Trajectory Planner

2014-04-01 Thread Marius Liebenberg
On 2014-04-01 22:45, Sebastian Kuzminsky wrote: > On 4/1/14 14:27 , Marius Liebenberg wrote: >> What was the verdict then, is this work going to be incorporated >> somewhere in the near future or will we have to wait until Robert has >> done more to it? > I'm not sure exactly what state it's in cu

[Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-01 Thread Sebastian Kuzminsky
I am pleased to announce the creation of a branch for stabilizing and releasing LinuxCNC 2.6. This marks the beginning of the 2.6 release process. Look for a 2.6.0~pre1 pre-release in the near future. The 2.6 branch does not contain either of the two big, hotly anticipated merge candidates, join