xenopeek wrote:The developers submit code to Cinnamon all the time, but you don't get these changes unless you run the development version of Cinnamon yourself or until a new release of Cinnamon is done. A new release of Cinnamon is preceded by a testing cycle to make sure all the code is working together as intended and stable enough to be released.
LMDE won't get a newer version of Cinnamon either, as there is no new release done for Cinnamon yet.
How is it that LMDE is waiting for a "new version" when it is a rolling release? Aren't rolling releases supposed to be updated all of the time, hence making it a "rolling" release? Frankly it sounds like LMDE isn't a rolling release at all, it sounds more like a distro that get's a quarterly update for it's releases.
I mean, I just don't get it. Alacarte used to be in Cinnamon and worked just fine. Then the Mint team takes out the working Alacarte and replaces it with a broken fork of Alacarte and proceeds to call it a stable release. Now it is finally fixed and no one is going to push it out to this so called stable release, they are going to just sit on it and wait for the next "stable" release. Why was the broken fork of Alacarte even put in 14? Why not wait until it works to put it in a stable release?
If the excuse your going to give is that you can't release fixes until they are all put together to make sure the next release is stable, how in the world did the broken fork of Alacarte ever make it into 14.
You know Xubuntu 12.10 also released with a broken menu editor, but you know what they did? They fixed it and released the fix to the users. I know, quite an odd concept. It's 2013 and I can't even edit an app menu on your "stable" release. This is precisely why the "year of Linux" is never going to happen. I just don't understand why Mint replaced a functioning app with a broken one, how is this any different than what Gnome has been doing? I thought that was the whole reason to fork Gnome Shell and create Cinnamon, to stop this stupid kind of developing.