[AT&T LG Optimus G] RodneyMcKay:
I would love for milestone builds to start. I completely agree that the nightlies are in really good shape, but from my perspective, at this point CM is focusing on new features before finishing migrating existing features and cleaning up new options for these existing long loved features. For example, I recently discovered that the problem with my CM Profiles and mobile data toggle is that Lollipop added new security to toggling this. Apparently it doesn't work with the CM SuperUser. http://xdaforums.com/android/apps-games/app-toggle-data-5-0-widget-to-toggle-t2937936 This notes that it is only an issue when SELinux is set to enforcing, but my attempts and other reading says it still doesn't work after using SELinux Mode Changer. While the mode changes in Phone Status, it doesn't allow the toggle to work.

I think things like that, regressions causing issues in large features, especially since there is a known solution, should be addressed first before releasing something as important as a Milestone build. Milestone are of increasing importance with the rate android is developing and CM is upgrading. Looking at the download page, the last stable builds is CM10.2 and now CM11 has basically stopped development in favor of CM12. Which brings up my next few points.

1) I wish I could contribute more to the community but I don't have the time or the programming experience. What I am good at is troubleshooting. Is the official JIRA bug tracker accepting bugs for CM12 yet? Last time I looked, the only response on CM12 bugs was that they are not being accepted as it is too new, being very actively developed, and only has nightly builds. The rules imposed on the Nightly Regression tracker also doesn't allow for posting issues with CM12, as it doesn't have a Milestone to compare against. I'd love to get some developers to look at a few issues, but get little to no response in this thread, and don't know of any other channel to report them to, so my efforts and troubleshooting experience silently goes to waste.

2) Many roms have a known issues list in the first post. In concept this is a great idea, but no one updates it when the community in the thread clearly identifies issues or other issues are fixed. Turning this into an working bug list and change/fix log would be awesome. This thread says GPS is broken, but that has been fixed. Bluetooth works but has a serious problem with having an incorrect mac address. This is not documented in the list. The fix that was floating around for CM11 was poorly documented and mostly in Russian when I found out about it. Unfortunately this doesn't work with the CM12 BT Mac issue. I don't know if it's a security issue like the MData toggle or something else. But it will cause problems in a known scenario and should be listed as such.

3) We need a good way to suggest improvements and either vote to show interest and/or receive feedback from developers that they agree and/or how troublesome it would be to accomplish. Android and CM are huge projects and many little details slip past everyone's eyes. For example CM Profiles, while in CM12, doesn't have support the new priority interruptions modes. I've had my rules cause my alarms to not sound in the morning making me late to work. This took a few days to figure out what was causing it. While priority interruptions modes are a great feature, I can't use the with the rules I have been using since CM10 to adjust my volume at night. Oh wait, I don't use profiles for volume at night. There are no time based triggers, that is another suggestion I've seen made many times around the internet. I can say however that there is now an option under "Preferred Network Type" for LTE. This didn't exist in the CM11 builds, you could switch to 2g from 4g but not back, now it looks like you can. I haven't tested if this works or not.

There are other issues with this e970 CM12 build at least for me.

-Random reboots

-bluescreen crash external modem(possiblely fixed by using the SolidGeeb kernel)

-green screen crash "Wcnss" while playing audio in airplane mode (only once so far, don't frequently listen to music outside of my car, was testing a problem with very low volume on left channel output, turns out to be issue with FauxSound)

-periodic audio skips via headphone jack (has been as frequent for me as .5 second every 15-20 in multiple all songs with poweramp, files test fine and worked in previous versions)

-massive 10+% per hour, mobile data battery drain(mostly isolated this to mdata)

-unconfirmed thoughts of wifi dropouts or possible broken support for "Keep Wi-Fi on during sleep: Always" ( many times, but not always, when turning on my phone screen the wifi indicator is missing)

-Wifi seems to not scan and auto connect to remembered networks reliably( many days at work I need to manually connect )

-battery indicator level doesn't seem to refresh while in sleep, I've turned phone on quickly to check battery and the level, and it seems the 10% per hour drain is better. By the time I can launch BBS the indicator suddenly drops 15+%.