I assume that if statetags was ready it would have been merged long ago.
So updating statetags to master branch is great -(and you probably should just merge it into linuxcnc's branch of statetags), it means someone needs to work on it till it works - it's a big change - i don't understand it and the people that do are not working on linuxcnc.
Also ya do we know the scope functionality of state tags?
It's been vaguely talked about for so long i don't know anymore.
My attempt was to fix a small problem so i could try to understand a bit about what i was doing, but I agree statetags is the goal - I personally just can't make that jump, i'm not that good to just look at small bits of the code and know what it is doing or if it is wrong code.
If it was completely up to me, i think I would:
-merge my work into 2.8 so at least the feedcode works for people in the next release.
- release 2.8 so people have a functional up to date version.
- start merging the unstable things like statetags and work on it - slightly broken master is a good motivator (obviously we are trying to avoid long breaks)
but at this point I can't even get people to answer the maillist for how to release so we are in pretty bad shape.
People are working on linuxcnc (I see Dewey commiting interesting things for instance) but there is no forward movement in this project as a whole.
Eventually I'll just do what I think is best at the moment and if people don;t like it they can come take this lead
