{ "uuid": [ { "value": "ea81e659-48e0-4eaf-ae3b-a30012102d0e" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-11T09:00:01+00:00" } ], "revision_uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "revision_log": [], "status": [ { "value": true } ], "uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "title": [ { "value": "Roll back or fix forward?" } ], "created": [ { "value": "2025-02-19T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:01+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2025\/02\/19\/back-or-forward", "langcode": "en" } ], "body": [ { "value": "\n

You deploy a code change but it creates an issue.<\/p>\n\n

Maybe it breaks a feature, adds a bug or takes down an environment completely.<\/p>\n\n

How do you resolve it?<\/p>\n\n

Larger releases will sometimes have a roll back plan that details how to revert to the previous release.<\/p>\n\n

This can be difficult, especially for large releases and ones that change the database schema or values.<\/p>\n\n

Because of the amount of change, diagnosing an issue in a large release can take time.<\/p>\n\n

If it's been a while since the prior release, it can be some time since the code that introduced the issue was worked on - making it harder to fix.<\/p>\n\n

I prefer to do small releases and do them often.<\/p>\n\n

Some releases contain a single commit which was made only minutes since the previous release.<\/p>\n\n

This makes it easier to identify the issue, fix it and deploy a new version.<\/p>\n\n

No rolling back database changes or reverting to previous releases.<\/p>\n\n

Small, iterative deployments are less risky than large infrequent ones, easier to fix and make changes available to end users sooner.<\/p>\n\n ", "format": "full_html", "processed": "\n

You deploy a code change but it creates an issue.<\/p>\n\n

Maybe it breaks a feature, adds a bug or takes down an environment completely.<\/p>\n\n

How do you resolve it?<\/p>\n\n

Larger releases will sometimes have a roll back plan that details how to revert to the previous release.<\/p>\n\n

This can be difficult, especially for large releases and ones that change the database schema or values.<\/p>\n\n

Because of the amount of change, diagnosing an issue in a large release can take time.<\/p>\n\n

If it's been a while since the prior release, it can be some time since the code that introduced the issue was worked on - making it harder to fix.<\/p>\n\n

I prefer to do small releases and do them often.<\/p>\n\n

Some releases contain a single commit which was made only minutes since the previous release.<\/p>\n\n

This makes it easier to identify the issue, fix it and deploy a new version.<\/p>\n\n

No rolling back database changes or reverting to previous releases.<\/p>\n\n

Small, iterative deployments are less risky than large infrequent ones, easier to fix and make changes available to end users sooner.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "1970-01-01T00:33:45+00:00", "guid": null, "hash": "bd41bad48401d8b39626d1b4c1fa46a3", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }