Editing Talk:04 Deployment & Release Management Procedure (section)

== 5. Deployment Process ==

=== 5.1 Pre-Deployment Activities: ===

==== 5.1.1 Environment Setup ====
* Check server health (CPU <80%, memory <70%).

* Verify database connectivity (e.g., MySQL, PostgreSQL) with test queries.

* Validate SSL certificates are active.

==== 5.1.2 Build and Packaging ====

* Run build scripts to create artifacts.

* Create database migration release script.

* Push artifacts to Artifactory with version tags.

* Tag build in Git (e.g., git tag v1.2.3) and push to repo.

==== 5.1.3 Checklist ====

* Confirm prod backups are complete.

* Verify network connectivity.

* Check disk space on prod servers.

* Ensure rollback artifacts are available in Artifactory. 

==== 5.1.4 Backups ====

* Create database backups.

* Backup configuration files.

* Test and validate restore process in staging to confirm backups are usable. 

=== 5.2 Deployment Execution: ===

==== 5.2.1 Checklist ====
* Verify artifact version matches Git tag.

* Check dependencies are installed.

==== 5.2.2 Execution ====
* Run deployment script or manual deployment. 

==== 5.2.3 Monitoring ====
* Watch server logs.

* Monitor CPU, memory, and response times.

=== 5.3 Post-Deployment Activities: ===

==== 5.3.1 Verification ====
* Run smoke tests (e.g., login, API health check) in prod within 10 minutes.

* Check performance (e.g., <200ms response time) manually or in Grafana dashboards.

* Confirm key features work via manual checks or automated scripts.

==== 5.3.2 Rollback ====
* Revert to previous artifact in Artifactory (e.g., app-v1.2.2.jar). 

* Restore database from last backup.

* Test rollback in staging first if time permits.

* Notify teams if rollback occurs.

==== 5.3.3 Notifications ====
* Email clients with release notes for major releases (e.g., new UI features). 

* Email specific stakeholders for hotfix.

* Notify stakeholders of any user-facing changes via email.

==== 5.3.4 Documentation ====
* Update release notes in GitHub Wiki with features, fixes, and issues.

* Record new environment settings (e.g., updated API keys) in Confluence.