>>11098
>We lose the current frontend, potentially breaking all boards that have customized their CSS. And things would look different. We may lose a couple features that we had in the frontend.

I don't know. Some people are already comfortable with the way things are. They did something similar in my other job with the software we used. People got pissed because of how hard things were to use compared to the old software they had.

>So the question is what are the pros and cons. Why disrupt the cozy? Is it worth it. Would it make our users happier.

Wellll we kinda had this happen before, almost a year ago. We migrated and were down for a while because there were more things to fix. We lost a lot of people from multiple boards after it happened. /v/ and /rus/ being the most notable boards being absent.

I dunno.

>I've already got a copy of the code all merged. We even had a few admins and testers find some bugs we've fixed already.

Do you have a virtual environment or production site where you test everything beforehand? Maybe making it near 100% "bug-free" before updating would be good

Most software updates in bigger companies get done during night shift since most people aren't up during that time, so that's another thing you can try depending on what you choose to do.