Ben Evans@Hex 1. Get good at SQL 2. Find out how long backups are kept for 3. Decouple the data change from the code change 4. Push the data change first, and have it corrupt the new fields are needed (maybe by setting defaults or polluting other parts of the records). 5. Bundle the code change with unrelated changes, and keep having the other changes fail QA 6. Wait until the uncorrupted backups have been purged 7. Push code change.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.