[Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 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,

Re: [Emc-developers] New Trajectory Planner

2014-04-02 Thread sam sokolik
Just to clarify.. This is all rob. I only try to test the crap out of it. :) sam On 04/01/2014 11:48 PM, Marius Liebenberg wrote: 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

Re: [Emc-developers] New Trajectory Planner

2014-04-02 Thread Marius Liebenberg
Very important as you seem to be the only one with the proper know how to make real sense of the test. I just look at the pictures and go aah!! On 2014-04-02 11:57, sam sokolik wrote: Just to clarify.. This is all rob. I only try to test the crap out of it. :) sam On 04/01/2014 11:48

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Marius Liebenberg
Because I dont know - who closes the bugs that have been tested or list items that are handled. Also how does the owner of the code get notified of the bug. There seem to be stuff that has been fixed a long time ago but the list is not updated. It mostly shows no owner for most of these. On

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Sebastian Kuzminsky
On 4/2/14 05:36 , Marius Liebenberg wrote: Because I dont know - who closes the bugs that have been tested or list items that are handled. Also how does the owner of the code get notified of the bug. There seem to be stuff that has been fixed a long time ago but the list is not updated. It

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Marius Liebenberg
Ok great to know someone is watching the list. I also reported another bug on the list to who I thing the owner could be. Lets see if he responds. Now if the owner does not respond, can anyone assist with the fix? If so how do we go about that? On 2014-04-02 17:21, Sebastian Kuzminsky wrote:

Re: [Emc-developers] [Emc-commit] master: gmoccapy_1_1_1 - macro handling bug

2014-04-02 Thread Sebastian Kuzminsky
On 4/2/14 11:56 , Norbert Schechner wrote: gmoccapy_1_1_1 - macro handling bug ver. 1.1.1 - small bug in macro button handling, if a macro was not found, gmoccapy raised an exception, because wrong variable name. Hi Norbert, please place your gmoccapy bug fixes in the branch called 2.6,

Re: [Emc-developers] [Emc-commit] master: new pyvcp_widgets

2014-04-02 Thread Sebastian Kuzminsky
On 4/2/14 12:14 , Michael Haberler wrote: new pyvcp_widgets this fixes http://sourceforge.net/p/emc/bugs/364/ Please apply in 2.6 and merge into master. -- Sebastian Kuzminsky --

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Lars Segerlund
Great, so no unified build ... this means rt-preemt is also not in emc 2.6 progress Please say I'm to pessimistic ? :-D / Lars Segerlund. 2014-04-02 8:50 GMT+02:00 Sebastian Kuzminsky s...@highlab.com: I am pleased to announce the creation of a branch for stabilizing and

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread EBo
Oh good god... Is there any way this could be brought in some how? On Apr 2 2014 2:09 PM, Lars Segerlund wrote: Great, so no unified build ... this means rt-preemt is also not in emc 2.6 progress Please say I'm to pessimistic ? :-D / Lars Segerlund. 2014-04-02 8:50

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Lars Segerlund
Just give it up, I followed rt-preempt developement for 4 years or so, and even measurement doesn't affect these guys, a good system can do rt-preempt and less than 10 us , under load, infact less jitter under heavy load than RTAI or xenomai, ( perhaps not less jitter, but smaller worst cases ).

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread sam sokolik
Just because it didn't make it into 2.6 doesn't mean it isn't going to happen. This isn't the end of the world. Have you seen the todo list? There have been a few calls for help http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Todo-2.6 As far as rt_preempt - I have tested it using the unified

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Lars Segerlund
What I am saying is this is the same talk as for the 2.4 release, a couple of years ago. Now there is nothing of importance in the 2.6 release described above, and it will take a couple of years for interesting stuff to make it to mainline. That puts it ouside my interest, I have been waiting

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread EBo
Fair enough, but I am having to say no to lots of projects and focus on my work with NASA, the UN, the IUCN, my thesis, and my two fun projects are rebuilding a CNC plasma torch the size of a small house, and if there is time, making some tools for my portable forge and foundry... Were the

Re: [Emc-developers] Announcing the LinuxCNC 2.6 branch

2014-04-02 Thread Gene Heskett
On Wednesday 02 April 2014 19:24:32 Lars Segerlund did opine: What I am saying is this is the same talk as for the 2.4 release, a couple of years ago. Now there is nothing of importance in the 2.6 release described above, and it will take a couple of years for interesting stuff to make it