release_decision:
  recommendation: GO | NO-GO | CONDITIONAL
  
  # Overall assessment
  confidence: 0.0-1.0  # 0.95+ for GO, 0.5-0.8 for CONDITIONAL, <0.5 for NO-GO
  risk_level: LOW | MEDIUM | HIGH | CRITICAL
  expected_impact: "Brief description of user-facing changes"
  
  # Decision rationale
  rationale: "Why GO/NO-GO/CONDITIONAL recommendation made"
  
  # Criteria checklist (20 items)
  criteria_passed: 18
  criteria_failed: 2
  criteria_details:
    - criterion: "All tests passing"
      status: PASS
      evidence: "CI/CD Evidence Card: 2,547 tests passed, 0 failed"
    - criterion: "Security scans clean"
      status: FAIL
      evidence: "Snyk found 1 high vulnerability in lodash@4.17.20"
      remediation: "Update lodash to 4.17.21+ or defer release"
  
  # Blocking issues (must resolve for GO)
  blocking_issues:
    - issue: "High-severity security vulnerability (CVE-2021-23337)"
      severity: HIGH
      assignee: "@security-team"
      eta: "2h (update dependency + rerun tests)"
    - issue: "Database migration not tested in staging"
      severity: CRITICAL
      assignee: "@backend-lead"
      eta: "4h (run migration, validate data integrity)"
  
  # Required follow-ups (can address post-release)
  required_followups:
    - action: "Add integration test for new API endpoint"
      priority: P1
      due: "Within 1 week"
    - action: "Update API documentation with new fields"
      priority: P2
      due: "Within 3 days"
  
  # Release metadata
  release_version: "v2.5.0"
  release_type: MINOR  # MAJOR | MINOR | PATCH | HOTFIX
  release_window: "2026-02-01 02:00-04:00 UTC (Sat night, low traffic)"
  rollback_plan: "See Rollback Plan section below"
  
  # Monitoring plan
  monitoring_duration: "48h"
  monitoring_thresholds:
    error_rate_max: "5%"  # Rollback if exceeded
    p95_latency_max: "500ms"
    traffic_drop_max: "20%"  # Potential outage indicator
  
  # Communication plan
  announcements:
    - channel: "Slack #engineering"
      message: "v2.5.0 deploying to production at 02:00 UTC Saturday"
      timing: "4h before deployment"
    - channel: "Email to customers (10k users)"
      message: "New features available: multi-currency support, bulk export"
      timing: "Monday 9am (after release validated)"
    - channel: "Status page (status.example.com)"
      message: "Scheduled maintenance: 02:00-04:00 UTC Saturday (minimal downtime expected)"
      timing: "48h before deployment"
  
  # Approvals
  approvals:
    engineering_lead: APPROVED
    product_manager: APPROVED
    security_team: PENDING  # Waiting for vulnerability fix
    compliance_team: NOT_REQUIRED  # No regulated data changes
  
  # DORA metrics tracking
  dora_metrics:
    deployment_frequency: "12 deployments this month"
    lead_time: "37 hours from commit to production"  # Commit at Thu 2pm → Deploy Sat 2am
    change_failure_rate: "8% (1/12 deployments required hotfix in past 30 days)"
    mttr: "43 minutes average (last 5 incidents)"

conditional_go_example:
  recommendation: CONDITIONAL
  confidence: 0.75
  reason: "Code coverage 78% (target 80%), but all critical paths tested"
  conditions:
    - "Deploy with increased monitoring (check dashboards every 30 min for first 4h)"
    - "On-call engineer must acknowledge and be available for immediate rollback"
    - "Add missing tests within 1 week (create Jira ticket)"
  monitoring_escalation: "If error rate >3% (vs normal 5% threshold), rollback immediately"

no_go_example:
  recommendation: NO-GO
  confidence: 0.3
  risk_level: CRITICAL
  reason: "Database migration will drop user_phone column, not backward-compatible"
  blocking_issues:
    - issue: "Migration drops column still used by v2.4.0 code"
      severity: CRITICAL
      impact: "Rollback to v2.4.0 will fail with SQL errors (missing column)"
      remediation: "Split into 2 releases: (1) Add new column, deprecate old column (2) Drop old column after 2 weeks"
      eta: "4 days (redesign migration, deploy phase 1, wait 2 weeks, deploy phase 2)"
  recommendation_action: "Defer release until migration redesigned for backward compatibility"

# Release Notes: v2.5.0 (February 1, 2026)

## 🎉 New Features

### Multi-Currency Support
You can now accept payments in 15 currencies (USD, EUR, GBP, CAD, AUD, JPY, CNY, INR, BRL, MXN, ZAR, SGD, HKD, NZD, CHF). Currency is detected automatically based on customer location, or can be manually selected at checkout.

**How to Use:**
1. Go to Settings → Payment Methods
2. Enable "Multi-Currency Support"
3. Select which currencies to accept
4. Currency converter uses live exchange rates (updated hourly)

**Benefits:**
- 🌍 Expand to international markets without currency friction
- 💰 Customers see prices in their local currency
- 📊 Revenue dashboard shows consolidated view in your base currency

---

### Bulk Export to CSV/Excel
Export orders, customers, and products in bulk. Supports CSV and Excel formats with customizable column selection.

**How to Use:**
1. Go to Orders → Select multiple orders (or click "Select All")
2. Click "Export" button → Choose CSV or Excel
3. Select which columns to include (Order ID, Customer Name, Total, Status, etc.)
4. Click "Download" → File downloads to your device

**Limits:**
- Up to 10,000 rows per export (Enterprise plan: unlimited)
- Export completes in 30 seconds for 10k rows

---

## 🐛 Bug Fixes

- **Fixed:** Order search not returning results for partial email addresses (now uses fuzzy matching)
- **Fixed:** Dashboard chart timezone incorrect (now respects user's timezone setting)
- **Fixed:** Mobile app crashes when uploading product images >5MB (now compresses images automatically)

---

## 🔧 Improvements

- **Performance:** Product listing page loads 40% faster (optimized database queries)
- **UX:** Added keyboard shortcuts (Ctrl+K to search, Esc to close modals)
- **Accessibility:** Screen reader support improved (WCAG 2.1 AA compliant)

---

## ⚠️ Breaking Changes

### API v1 Deprecated (Sunset: August 1, 2026)
API v1 (`api.example.com/v1/*`) is deprecated and will be shut down on August 1, 2026. Please migrate to API v2 (`api.example.com/v2/*`) before this date.

**Migration Guide:** [docs.example.com/api-v1-to-v2-migration](https://docs.example.com/api-v1-to-v2-migration)

**What Changed:**
- Authentication: Basic Auth → JWT tokens (see [Authentication Guide](https://docs.example.com/auth))
- Pagination: `page` parameter → `cursor` (more efficient for large datasets)
- Error responses: Now return RFC 7807 Problem Details JSON format

**Support:** Contact support@example.com if you need help migrating before August 1.

---

## 🔒 Security Updates

- **Updated:** JWT library to fix [CVE-2025-1234](https://nvd.nist.gov/vuln/detail/CVE-2025-1234) (high severity)
- **Updated:** Node.js from 20.10.0 → 20.11.1 (security patches for HTTP/2)

---

## 📦 What's Next

Coming in v2.6.0 (March 2026):
- 📧 Email campaign builder (drag-and-drop editor)
- 🤖 AI-powered product recommendations
- 📱 Mobile app redesign (iOS + Android)

---

**Questions?** Contact support@example.com or join our [community forum](https://community.example.com).

# Migration Guide: API v1 → API v2

## Overview
API v2 introduces JWT-based authentication, cursor-based pagination, and RFC 7807 error responses. All endpoints return the same data, but request/response formats have changed.

**Deadline:** Migrate before August 1, 2026 (API v1 shutdown)

---

## Code Changes Required

### 1. Authentication (Basic Auth → JWT)

**Before (API v1 with Basic Auth):**
```javascript
const response = await fetch('https://api.example.com/v1/orders', {
  headers: {
    'Authorization': 'Basic ' + btoa(username + ':' + password)
  }
});

// Step 1: Get JWT token (one-time, cache for 1h)
const authResponse = await fetch('https://api.example.com/v2/auth/token', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ apiKey: 'your-api-key', apiSecret: 'your-api-secret' })
});
const { token } = await authResponse.json();

// Step 2: Use JWT token for API requests
const response = await fetch('https://api.example.com/v2/orders', {
  headers: {
    'Authorization': `Bearer ${token}`
  }
});

// Page 1
const page1 = await fetch('https://api.example.com/v1/orders?page=1&limit=100');

// Page 2
const page2 = await fetch('https://api.example.com/v1/orders?page=2&limit=100');

// Page 1
const page1Response = await fetch('https://api.example.com/v2/orders?limit=100');
const page1Data = await page1Response.json();
// Response: { data: [...100 orders], nextCursor: "eyJpZCI6MTAwfQ==" }

// Page 2 (use nextCursor from page 1)
const page2 = await fetch(`https://api.example.com/v2/orders?limit=100&cursor=${page1Data.nextCursor}`);

{
  "error": "Order not found",
  "code": "ORDER_NOT_FOUND"
}

{
  "type": "https://docs.example.com/errors/order-not-found",
  "title": "Order Not Found",
  "status": 404,
  "detail": "Order with ID 'abc123' does not exist or has been deleted",
  "instance": "/v2/orders/abc123",
  "traceId": "550e8400-e29b-41d4-a716-446655440000"
}

if (!response.ok) {
  const error = await response.json();
  console.error(`Error ${error.status}: ${error.title} - ${error.detail}`);
  console.error(`Trace ID for support: ${error.traceId}`);
}

---

## Rollback Plans

### Rollback Type 1: Code Rollback (Revert Git Commit)

**When to Use:**
- New code has bugs causing errors/crashes
- Performance regression (p95 latency >2x baseline)
- Feature causing user complaints (UX issues)

**Procedure:**
```bash
# 1. Assess situation (check error logs, dashboards)
echo "Error rate: 12% (baseline: 1%) - ROLLBACK NEEDED"

# 2. Revert last commit on main branch
git revert HEAD
git push origin main

# 3. CI/CD automatically triggers build + test + deploy (5-10 min)
# Monitor CI/CD pipeline in GitHub Actions / GitLab CI

# 4. Verify rollback successful
curl https://api.example.com/health
# Expected: {"status": "healthy", "version": "v2.4.0"}

# 5. Notify stakeholders
# Slack #engineering: "Rolled back v2.5.0 due to high error rate (12%). v2.4.0 restored. Investigating root cause."

# 1. Assess situation (check database logs, slow query log)
psql -h prod-db.example.com -U admin -d myapp -c "SELECT pg_stat_activity WHERE state = 'active' AND query_start < NOW() - INTERVAL '30 seconds';"
# If many slow queries related to new column/index → rollback needed

# 2. Stop application traffic (prevent new writes during rollback)
kubectl scale deployment myapp --replicas=0
# Or: Use feature flag to disable writes

# 3. Run rollback migration
npm run migrate:rollback
# This reverts last migration (tested in staging before release)

# 4. Verify database state
psql -h prod-db.example.com -U admin -d myapp -c "\d users"
# Verify old schema restored (e.g., `user_phone` column still exists)

# 5. Restore application traffic with old code version
kubectl set image deployment/myapp myapp=myapp:v2.4.0
kubectl scale deployment myapp --replicas=4

# 6. Verify application healthy
curl https://api.example.com/health
# Expected: {"status": "healthy", "version": "v2.4.0", "dbMigrationVersion": "20260125_add_user_phone"}

# 1. Identify bad config change
kubectl describe configmap myapp-config
# Review recent changes (who changed what when)

# 2. Rollback to previous ConfigMap revision
kubectl rollout history configmap/myapp-config
# Output:
# REVISION  CHANGE-CAUSE
# 1         Initial config
# 2         Updated Redis URL (working)
# 3         Updated DATABASE_URL (broke app)

kubectl rollout undo configmap/myapp-config --to-revision=2

# 3. Restart pods to pick up old config
kubectl rollout restart deployment/myapp

# 4. Wait for rollout to complete
kubectl rollout status deployment/myapp
# Output: "deployment "myapp" successfully rolled out"

# 5. Verify application healthy
curl https://api.example.com/health

# Error rate (percentage of HTTP 5xx responses)
sum(rate(http_requests_total{status=~"5.."}[5m])) / sum(rate(http_requests_total[5m])) * 100

# Alert rule:
- alert: HighErrorRate
  expr: sum(rate(http_requests_total{status=~"5.."}[5m])) / sum(rate(http_requests_total[5m])) > 0.05
  for: 5m
  labels:
    severity: critical
  annotations:
    summary: "Error rate >5% for 5 minutes"
    description: "Current error rate: {{ $value | humanizePercentage }}"

# P95 latency
histogram_quantile(0.95, sum(rate(http_request_duration_seconds_bucket[5m])) by (le))

# P99 latency
histogram_quantile(0.99, sum(rate(http_request_duration_seconds_bucket[5m])) by (le))

# Alert rule:
- alert: HighLatency
  expr: histogram_quantile(0.95, sum(rate(http_request_duration_seconds_bucket[5m])) by (le)) > 0.5
  for: 10m
  labels:
    severity: warning
  annotations:
    summary: "P95 latency >500ms for 10 minutes"

# Requests per minute
sum(rate(http_requests_total[1m])) * 60

# Alert rule (traffic drop):
- alert: TrafficDrop
  expr: sum(rate(http_requests_total[5m])) < 0.8 * sum(rate(http_requests_total[5m] offset 1h))
  for: 5m
  labels:
    severity: critical
  annotations:
    summary: "Traffic dropped >20% compared to 1 hour ago"

# Checkout conversion rate (orders / cart views)
sum(rate(orders_completed_total[5m])) / sum(rate(cart_views_total[5m])) * 100

# Alert rule:
- alert: ConversionRateDrop
  expr: sum(rate(orders_completed_total[5m])) / sum(rate(cart_views_total[5m])) < 0.9 * (sum(rate(orders_completed_total[5m] offset 1d)) / sum(rate(cart_views_total[5m] offset 1d)))
  for: 10m
  labels:
    severity: critical
  annotations:
    summary: "Checkout conversion rate dropped >10% vs yesterday"

# Count deployments in last 30 days
git log --since="30 days ago" --grep="deploy" --oneline | wc -l
# Output: 12 deployments

# Frequency: 12 / 30 = 0.4 deployments/day = 2.8/week (HIGH)

# Commit timestamp
git log --format="%H %ai" -1 abc123
# abc123 2026-01-30 14:00:00 -0500

# Production deployment timestamp
git log --grep="deploy v2.5.0" --format="%ai" -1
# 2026-02-01 02:00:00 -0500

# Lead time: 37 hours (Thu 2pm → Sat 2am)

# Count total deployments in last 30 days
TOTAL_DEPLOYS=12

# Count deployments requiring hotfix/rollback
git log --since="30 days ago" --grep="rollback\|hotfix" --oneline | wc -l
# Output: 1

# Change failure rate: 1 / 12 = 8.3%

# Incident log (last 5 incidents)
Incident 1: Detected 2026-01-15 03:00, Resolved 03:25 → MTTR: 25 min
Incident 2: Detected 2026-01-18 10:00, Resolved 10:50 → MTTR: 50 min
Incident 3: Detected 2026-01-22 14:00, Resolved 14:20 → MTTR: 20 min
Incident 4: Detected 2026-01-28 08:00, Resolved 08:45 → MTTR: 45 min
Incident 5: Detected 2026-01-29 19:00, Resolved 20:15 → MTTR: 75 min

# Average MTTR: (25 + 50 + 20 + 45 + 75) / 5 = 43 minutes

📦 **Production Deployment: v2.5.0**

**When:** Saturday, February 1, 2026 at 02:00-04:00 UTC (Friday 9pm-11pm EST)

**What's Deploying:**
- Multi-currency support (15 currencies)
- Bulk export to CSV/Excel (10k row limit)
- Performance improvements (40% faster product listing)
- Security fix: JWT library updated (CVE-2025-1234)

**Expected Impact:**
- Downtime: 2-3 minutes during deployment (database migration runs)
- Traffic: Low (2am UTC = night in US/Europe)
- Rollback plan: Documented, tested, <5 min MTTR

**Monitoring:**
- On-call: @john-doe (primary), @jane-smith (backup)
- Dashboard: https://grafana.example.com/d/production
- Alerts: #production-alerts (error rate >5% triggers auto-rollback)

**Post-Deployment:**
- First 4h: Check dashboard every 30 min
- If issues: Page @john-doe, incident commander decides GO/NO-GO for rollback

**Questions?** Reply in thread or DM @release-manager

🚀 Let's ship it!

Subject: New: Accept Payments in 15 Currencies 🌍

Hi [Customer Name],

We're excited to announce **multi-currency support** is now live! You can now accept payments in 15 currencies, making it easier for your international customers to shop.

**What's New:**
✅ 15 supported currencies (USD, EUR, GBP, CAD, AUD, JPY, and more)
✅ Automatic currency detection based on customer location
✅ Live exchange rates (updated hourly)
✅ Revenue dashboard shows consolidated view in your base currency

**How to Get Started:**
1. Go to Settings → Payment Methods
2. Enable "Multi-Currency Support"
3. Select which currencies to accept
4. Your customers will now see prices in their local currency!

[Watch 2-Min Tutorial Video →]

**Also New in v2.5.0:**
- Bulk export orders to CSV/Excel (up to 10,000 rows)
- Faster product listing page (40% speed improvement)
- Improved mobile app (fixes image upload crash)

**Need Help?**
- Documentation: docs.example.com/multi-currency
- Support: support@example.com
- Live chat: Click the chat bubble in your dashboard

Thanks for being an awesome customer! 🎉

The [Company Name] Team

---

P.S. Have feedback on multi-currency? Reply to this email—we read every message!