From 2e60b7657043654f38cc983053de916a660609a3 Mon Sep 17 00:00:00 2001 From: MikeGrace Date: Fri, 9 Aug 2024 16:49:26 -0500 Subject: [PATCH] release management post --- ...nt-basics => 2024-08-09-release-management-basics.md} | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) rename _posts/{2024-08-09-release-management-basics => 2024-08-09-release-management-basics.md} (99%) diff --git a/_posts/2024-08-09-release-management-basics b/_posts/2024-08-09-release-management-basics.md similarity index 99% rename from _posts/2024-08-09-release-management-basics rename to _posts/2024-08-09-release-management-basics.md index 2c6bc58..6dec628 100644 --- a/_posts/2024-08-09-release-management-basics +++ b/_posts/2024-08-09-release-management-basics.md @@ -1,12 +1,9 @@ -```yaml +--- title: "Release Management Basics" - layout: post - categories: - -- SDLC -``` + - SDLC +--- Good release management is balancing system integrity with getting new features and fixes to customers at speed. Good release management is also agile, adjusting as your teams and system change. How can you make sure that your features are getting to production as quickly as possible with the least amount of friction and risk as possible? How do you know when you are maintaining a healthy balance? Use this high-level guide help identify where your teams may have opportunities to improve.