On 3 April 2014 12:30, Mark Tucker <[email protected]> wrote:

> Exactly what is the 2.6 branch bringing to the table at this point??
> As someone has already stated,why can it not be a case of switch the new
> TP on/off in the ini.
> It is the only way it will get tested properly.

If there was an "inner circle" that made this decision, then I wasn't
part of it.
But: Something as big as a new TP would always be expected to live in
the "master" branch for a while where adventurous users could
experiment with it and shake out the bugs.
The "Released" versions are meant to be tested and known-good.

2.6 will introduce the things introduced to Master since the 2.5
release (which was 31st March 2012, quite a long time ago).
This includes things such as G-code remapping (including Python access
to interp state), a couple of new GUIs (gscreen and gmoccapy) and some
more HAL components.

I think there was a list somewhere, it is more than you might guess,
but less than was expected.

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto

------------------------------------------------------------------------------
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to