Feature Request

phillc54 wrote:

snowgoer540 wrote:

So Phill has mentioned similar, and I'm not sure I understand why? Once it's released, don't updates just work as usual, or no?

Yes, provided that any update is not reliant on a feature of master that is not in the release version.

rodw wrote:

I struggled to understand Phill's comment but my point is 2.8 should revert to updates being released on point releases to 2.8 and any new features should be restricted to 2.9 master branch. Lets revert to the development cycle that should always have been in place... Users need a stable system to work with if they want to change screen sets or add their own enhancements..

Or live dangerously on master which is the only life I've ever known..

rodw wrote:

Bugs??? Whats the test pilot been doing? I understand bug fixes can be push as they are resolved.

phillc54 wrote:

You may need to do a make clean after switching branches then to be safe redo the ./autogen.sh and ./configure --with-realtime=uspace

Edit: I did think of renaming them like you did but then someone will complain that they press Torch On and it doesn't turn on...

> cd linuxcnc-dev/src
> git checkout 2.8
> ./autogen.sh
> ./configure --with-realtime=uspace
> make
> sudo make setuid

> git clone git://github.com/linuxcnc/linuxcnc.git linuxcnc-dev

rodw wrote:

I struggled to understand Phill's comment but my point is 2.8 should revert to updates being released on point releases to 2.8 and any new features should be restricted to 2.9 master branch. Lets revert to the development cycle that should always have been in place... Users need a stable system to work with if they want to change screen sets or add their own enhancements..

snowgoer540 wrote:

Used the following steps, seems to have the same results, my torch button is still named what I named it. What am I doing wrong?

ls -l ~/linuxcnc/configs/<your_plasma_config>/plasmac/plasmac_axis.py