tl;dr

We are now aiming to deliver the PrismicDB migration by mid-February. We are clearing the path by closing all minor projects we are having in parallel (e.g. pricing, high traffic during the holiday season). This week will offer more clarity on the remaining time before reaching the target.

Goals for This Week:

Closing parallel projects:

- We already deployed the new pricing for new repository creations last week and were planning to migrate our current user base last week as well. The migration will finally start on Tuesday this week. The plan is still to wait until the end of the repositories' billing cycle to perform the upgrade. Hence, it will take one month to complete all the monthly plans and a year for the repos with a yearly commitment.

- After the incident with Bershka last October (the API was down for more than one hour), the team jumped quickly into corrective actions and optimization to prevent another incident. The result is that Bershka had a pretty smooth winter sales season. We want to gather and share the results with the company.

Getting back to PrismicDB migration

Once the other projects are delivered we will get back to the Prismic DB migration.

- Working on the database made us rework many internal systems. One of them was the way we are managing master locales. In our writing room, the master locale used to be set once and for all. Changing the master locale isn't as easy as setting a flag because our search engine, Apache Lucene, relies on languages to optimize the search queries.

We will communicate about this feature to our users by the end of the week.

- The other goal is to share the roadmap on when we should meet our next milestones.