On Tue, Jul 22, 2014 at 08:57:21PM +0100, Steve Blackmore wrote:
> On Tue, 22 Jul 2014 08:06:43 -0600, you wrote:
> >
> >The new trajectory planner is not in 2.6.  It's in the master branch and
> >will be part of 2.7. 
> 
> Why? 

The most recent bugfix in the new trajectory planner was yesterday.
It looks like rotary axes didn't work right before that.  Other
recent changes have fixed incorrect threading behavior.  It has not
seen wide use on a variety of real machines.  It is simply not ready
to be in the stable release yet.

> Time and effort wasted getting yet another 2.6 out rather than
> actually

We've previously fallen into the trap before of waiting for "just
one more feature" to stabilize before releasing the good work we
already have.  2.6 has some wonderful new stuff, and if you don't
need it, that's fine, but your needs are not universal.  You are
wrong that the 2.6 work is a waste of time.

Here is what I do know for sure: if the new planner is important to
you, you SHOULD BE TESTING IT to make sure it's ready for 2.7.  

Since you are obviously affected by current planner limitations,
doing testing in your environment would not only help YOU
immediately, but would help everyone have a more stable 2.7 release.
It may also help the 2.7 release come sooner.

You have easy access to this code.  It has never been easier to test
master builds, now that buildbot makes packages automatically (which
is, by the way, another thing that Seb, who you accuse of wasting
time and effort, has done for you and the project.)

Chris

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to