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.

So full speed ahead with ideas, got it!!

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: 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..

I guess I understand what you're getting at. But what about bugs that get squished after release?

As far as the users go they don't have to update...

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

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

I'd say we squished them all, but that seems like a silly thing to do to cause an unnecessary jinx LOL

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...

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?

Only line I didnt use was:

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..

That is how it works if the user doesn't change the source repository. All updates between 'point' releases are on the buildbot so if users wish to take advantage of them they can. Nothing has changed.

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?

Try: and make sure it is a link pointing to the plasmac source directory

indeed it is...

I guess I could just delete the directory and start again?

It's not a huge deal, but I'd just be worried I wouldn't pick something up for some reason.