Skip to main content
Skip table of contents

Deployment Schedules

Hey everyone! If you've had a ticket with us resolved in the past few weeks, you may have heard your account manager tell you that the issue has been fixed, and that it will go live in the near future. I wanted to take this opportunity to do a quick dev dive and explain why that is, and what you can expect for tickets in the future.

The development team has recently switched to a weekly deployment schedule. Instead of pushing out fixes whenever they're ready, we now push all code changes live at the end of our sprints late at night (see the dev dive on Agile for more details). This helps us in a few different ways. Firstly, it means that we can fix any conflicts caused by two or more developers working on the same code before any of that code hits the platform. Secondly, it gives us additional opportunities to quality control on different data sets before deploying to client websites, meaning we create fewer bugs. And lastly, it gives us one final chance to quality control on live client websites during every deploy, so that even if a bug slips through, we can catch it in the middle of the night when there are fewer users on the platform and make the necessary fixes before the following day. This kind of deployment schedule is common across most major tech platforms, and really helps keep the code base as pristine as possible.

What this means for you is that some of your tickets may have to wait for a few days before the fix is pushed live. For pressing issues (such as errors with ecommerce), we can push hotfixes immediately, and if your ticket is about something unique to your website, you may see the fix outside of the deployment schedule because platform code didn't have to be altered. If your account manager does let you know that the fix is staged for the next deployment, however, just wait for the next Wednesday and everything should be good to go.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.