08-11-2024, 01:50 PM
(This post was last modified: 08-24-2024, 05:29 PM by pinkgothic.)
EDIT:
We current expect downtime to start around 14:00 on 25.08.2024 and last for at least 3 or 4 hours.
Realtalk: Maybe you, too, have gotten a bit tired of hearing about the mythical recode.
Well, we have news for you! We're sick of it, too. It's been over three doggone years. We're tired, bro, just tired. Enough is enough. It's time. The recode is here right now... er, for values of 'right now' that are scheduled for later this month.
Okay, okay, our staging server is making confused, anxious noises as I say this, but we've unleashed some testers on it and the main functionality should be more or less available. It will probably not die horribly once more people are using it. But even if it does, the recode is pretty sexy and the developers can fix it much faster!*
All humour aside, it's true:
We'll be migrating everything to the new code in a couple of weeks (the migration is currently planned for 25.08.2024). The new code will allow future development that has been sorely lacking these past three years. With the old site code, if we had struggled and sworn a lot, we might have been able to add four new small features in an entire year. With the new code, we're confident we can tackle a solid chunk more.
What do you need to know about the migration?
1. There will be a substantial downtime during that phase, mostly because much of our database needs to rebuild itself without poking itself in the eye.
2. The new user interface is very different! Please be emotionally prepared that your old workflows will require different clicks in different places and that the site will fundamentally feel very different! You can and should make suggestions about improvements if something really bugs you! :) But please don't freak out about the changes, and give yourself a few days to get used to things before you ask for changes.
3. Once the site is accessible again, you'll be able to continue where you left off. If you notice anything missing, we'll still have the old database around and we'll be able to mend whatever went pear-shaped.
We current expect downtime to start around 14:00 on 25.08.2024 and last for at least 3 or 4 hours.
Realtalk: Maybe you, too, have gotten a bit tired of hearing about the mythical recode.
Well, we have news for you! We're sick of it, too. It's been over three doggone years. We're tired, bro, just tired. Enough is enough. It's time. The recode is here right now... er, for values of 'right now' that are scheduled for later this month.
Okay, okay, our staging server is making confused, anxious noises as I say this, but we've unleashed some testers on it and the main functionality should be more or less available. It will probably not die horribly once more people are using it. But even if it does, the recode is pretty sexy and the developers can fix it much faster!*
* terms and conditions apply.
All humour aside, it's true:
We'll be migrating everything to the new code in a couple of weeks (the migration is currently planned for 25.08.2024). The new code will allow future development that has been sorely lacking these past three years. With the old site code, if we had struggled and sworn a lot, we might have been able to add four new small features in an entire year. With the new code, we're confident we can tackle a solid chunk more.
What do you need to know about the migration?
1. There will be a substantial downtime during that phase, mostly because much of our database needs to rebuild itself without poking itself in the eye.
2. The new user interface is very different! Please be emotionally prepared that your old workflows will require different clicks in different places and that the site will fundamentally feel very different! You can and should make suggestions about improvements if something really bugs you! :) But please don't freak out about the changes, and give yourself a few days to get used to things before you ask for changes.
3. Once the site is accessible again, you'll be able to continue where you left off. If you notice anything missing, we'll still have the old database around and we'll be able to mend whatever went pear-shaped.