This services as the CURRENT update timeline for our migration from the old SoMee.social to the NEW SoMee.social. Please refer to this for any future updates, and don't forget to check out the roadmap too: https://devs.somee.social/somee-roadmap/
On May 28, 2021, we'll be taking down both beta.somee.social and somee.social web sites and apps. The site will be placed in maint mode for about 4-5 hours. This is NECESSARY because we have to migrate and merge users, data, posts, and objects, to ensure that all the information is properly migrated. We also need to do testing (smoke tests and QA tests) to ensure the migration was successful, as well as DNS changes, to ensure that our plan to migrate is successful.
NOTE: Times here are approx, we may push it up or down a few hours, given the availability of staff, but this is what we are shooting for:
- May 28, 2021, at 10 pm PST: We'll be taking both beta.somee.social and somee.social offline
- May 28, 2021, at 10:45 pm PST: We'll begin the migrations of data from site to site, as well as the DNS and infrastructure changes to move beta to the main somee.social
- May 28, 2021, at 11:30 pm PST: We'll continue to monitor the migrations script, it should take several hours to finish.
- May 29, 2021, at 12:00 am PST: We'll confirm migrations finished, confirm DNS changes migrated, and that they are propagated
- May 29, 2021, at 12:30 am PST: We'll tentatively re-enable somee.social and move the OLD somee.social to an archive.somee.social domain name mainly in read-only mode.
- May 29, 2021, at 12:35 am PST: QA will begin smoke tests and quality tests of somee.social
- May 29, 2021, at 1:00 am PST: We'll have our initial QA results, and begin work on any bugs, issues that are being affected
- May 29, 2021, at 2:00 AM PST: We should have everything re-enabled for everyone to use, and the new site on somee.social and old site on archive.somee.social
In case something goes wrong, or the QA tests state that we are not viable on somee.social, we can undo the migration pretty quickly, and have the old somee.social back on somee.social within 20 minutes.
We'll then investigate WHY the migration failed, and go form there.
The merge of data from Production (somee.social) to the beta (beta.somee.social) and then subsequently move to somee.social is COMPLEX - only because we have existing posts, users, and objects in the OLD site, and NEW site and need to retain both sets of data. (mouth full lol) suffice to say, we have to make sure that all data is migrated and linked properly - so that people don't lose their posts, images, or data and that the accounts are properly reflected as well.
Potential for Data Loss
There is a slight potential for some data loss if the information cannot be brought over, but we'll evaluate each case on a user-by-user basis and let them know of anything NOT transitioned due to any conflicts that may arise.
Leave a Reply