[Motorola Droid 4] Jishkah:
The phone is rock solid for me, too. To be honest, the only bugs that I've seen thus far have been either cosmetic bugs, or small bugs with CM12.1, as a whole (NOT device-specific), and even those are rare - rare enough to make the ROM about as stable as any other phone's stock OS. I haven't had the WiFi issue pop up since my first day, either. The only remaining "bug" - and I use that word in quotations, because it's not exactly a bug - is that I sometimes receive an App Not Responding/App Crashed notification, which I attribute to the phone's lack of RAM. Even then, the processes automatically restart, so it's effectively a non-issue.

It feels ****ing fantastic to have the latest version of Android on a phone that's almost three and a half years old. Seriously, hats off to the community for maintaining this phone for as long as they have. I love you guys.

EDIT: Since I'm commenting, does anybody know if there's a way to essentially "edit" the Symbols key pop-up menu with keys of my choice, outside of flashing files via Recovery? In CyanogenMod 10, for example, I seem to remember it having a tilde (~) key (on the upper-left corner, actually), but it disappeared in CyanogenMod 11. CyanogenMod 11 had < and >, but they disappeared in CyanogenMod 12. Actually, it'd be pretty cool to have Emoji access attached to the Symbols key, as well, but that almost sounds like it'd require a re-write of the Symbols key pop-up interface.

EDIT #2: I did, actually, just now encounter a bug that's been there since CyanogenMod 11. For some reason, every once in a while, I'll receive a "Message Not Sent" notification from the stock SMS/MMS app - but it won't "connect" to any one message. I'll tap it, and it'll just open the Messaging app, and it won't go away. I swipe it away from the Notifications List, but it always comes back as soon as I re-open the Messaging app. This usually persists until I perform a clean wipe of the ROM Slot and install a new ROM. It's generally harmless, but it's still an annoying notification that always comes back if I re-open the Messaging app - I can obviously filter notifications like that, but Pushbullet still picks them up (oddly enough) and I want to be able to see the notification on the off chance that a message that I send actually can't be sent.

For the record, I don't have any issues sending messages, which makes it odd that I received this message, to begin with. It also stacks, oddly enough - I could be using my phone, no problems, and then I'll get this notification in the Notification Drawer. Okay, no problem; I'll just ignore it. But then, after a week or so, there's a (2) next to the notification, meaning that I received more than one "Message not sent" notification.

Anyway, I attached two screenshots of what I mean. Unfortunately, I wasn't able to make a Screenshot of the Notification Drawer, but the notification says "Message not sent: Touch to review the message and try again". If I touch the notification, it opens up a new message - like the screenshot shows - but the notification won't go away. If I close the app and swipe the notification away, it generally stays away until I either receive a text, or open the Messaging app - and then it'll show up again. The only difference between what my settings are and what I assume the majority's settings are is that I have Delivery Receipts enabled for both SMS and MMS. Besides that, I sometimes have issues with sending MMS messages - taking up to an hour for an MMS of mine to send, at times - but I never receive a "Message not sent" notification, and it usually just says "Sending" until it finally goes through.

Is there a way that I can "debug" this and send a log of what goes on when my phone receives this notification and I tap it? It's been an issue since CyanogenMod 11, so it's definitely not just an aspect of running a CM12.1 Nightly - to be honest, I figured the problem was fixed between CM11 and CM12.1 until it finally popped up two weeks after installing CM12.1.