OK folks heads up. Some of you might be seeing a LOT of activity in tracker today. I'm going to tell you what is going on so you can act on things if you want to. We are exploring options for Tracker replacement or repair to make it a better experience for devs, but it is CHOCK FULL of old tickets. Stuff that has been there for years. Yes, it is our fault, long term. These are items we were never able to get around to. And SOME of these are things that either no longer matter, or the community has worked around, or were fixed in some other way. In any case, we are sorting through the very old tickets and closing each, WITH an explanation of why. IF YOU DISAGREE w/ the closing reason and still feel the ticket is worthy of pursuit, and can both show a repro of the issue and make your case, please CREATE A NEW TICKET with the information. It is impossible for us to properly sort these without doing something like this. I apologize, these should likely have been sorted and handled long before I (or much of current engineering leadership, to be fair) were here. What this does is provide us an opportunity to pull up those still critical ERs and bugs, refresh our understanding of why you might want the changes AND get current, working code samples. If you want to yell at someone about this, yell at me. After many hours of knocking our heads together, this was the most effective and optimized way to really get to the heart of which items matter most from a very, VERY large stack. Just remember, I love you all. Let the hazing begin. ❤️