Confirmed users
120
edits
CloudServices/Loop/MySQL: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Ametaireau (talk | contribs) No edit summary |
Ametaireau (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
=== Tentative schedule === | === Tentative schedule === | ||
We need to have this landed on our prod stack '''before''' we hit firefox 35 release. | We need to have this landed on our prod stack '''before''' we hit firefox 35 release if possible. | ||
Depending if we can drop the data or not, the schedule would change. | |||
In case the data can be dropped but not after a certain point in time, we need to define what this time is and it would mean that we deploy something early on: | |||
* '''28 of october''': Code ready, we are ready for deployment; | * '''28 of october''': Code ready, we are ready for deployment; | ||
| Line 13: | Line 16: | ||
* Once it's deployed to staging and verified, we can deploy to prod. | * Once it's deployed to staging and verified, we can deploy to prod. | ||
* Once this is done, we plan to have some feature-freeze time when we have time to investigate how MySQL is behaving and to any bugfix that's needed. | * Once this is done, we plan to have some feature-freeze time when we have time to investigate how MySQL is behaving and to any bugfix that's needed. | ||
In case we need data migration, it means that we need to write the scripts to do this data migration, decide on how to deal with that and make it happen before the firefox 35 release. | |||
=== Data migration === | === Data migration === | ||