Academic Pipeline Deprecation and Migration Notice

Role: Lead Data Infrastructure Engineer managing high-performance scientific computing and research data environments.

Context

• Legacy pipeline being decommissioned: {{legacy_pipeline_name}}
• Final sunset and cut-off date: {{target_sunset_date}}
• Successor infrastructure or tool: {{new_platform_name}}
• Impacted scientific workflows: {{research_workloads_impacted}}
• Dedicated migration documentation: {{migration_guide_url}}
• Technical support escalation point: {{support_contact_channel}}

Task

Draft an informative and supportive deprecation notice email to researchers and academic staff using {{legacy_pipeline_name}}, outlining key milestones, why the change is occurring, and how to migrate to {{new_platform_name}}.

Method

1. Create a clear broadcast subject line containing pipeline name, action required, and sunset date.
2. Announce the planned decommissioning of {{legacy_pipeline_name}} and state the upgrade rationale.
3. Outline the key technical improvements offered by {{new_platform_name}} (e.g., speed, reproducibility, scalability).
4. Itemize the phased sunset schedule from feature freeze to final compute cluster shutdown on {{target_sunset_date}}.
5. Explain specific impacts on active workflows within {{research_workloads_impacted}}.
6. Direct researchers to {{migration_guide_url}} for code migration scripts and containerized templates.
7. Detail hands-on support windows, office hours, and contact instructions via {{support_contact_channel}}.

Constraints

• MUST clearly specify the exact date when compute jobs on {{legacy_pipeline_name}} will be terminated.
• MUST NOT use overly aggressive administrative tone; maintain an enabling, researcher-focused perspective.
• Keep total length between 300 and 450 words.
• Ensure documentation links and office hour details are prominent.

Output format

• Subject: NOTICE: Transitioning from {{legacy_pipeline_name}} to {{new_platform_name}} [Timeline & Action Required]
• Executive Announcement (1 paragraph)
• Phased Deprecation Timeline (bulleted chronological list)
• Benefits of {{new_platform_name}} (3 short bullet points)
• Migration Instructions & Documentation (bulleted with link placeholder)
• Support Channels & Office Hours (1 concise closing section)

Self-review

• Is {{target_sunset_date}} explicitly stated for both freeze and termination phases?
• Does the email provide immediate, actionable paths to {{migration_guide_url}}?
• Are affected workloads in {{research_workloads_impacted}} addressed directly?