Comms are available to end users

Oct 13, 2025 by pynkocean.com 24 views

✈ Airflow - Create Initial Comms/Timelines for Airflow Migration

As the maintainers of Airflow, we are committed to providing a seamless migration experience for our customers. To achieve this, we need to create a clear timeline and communication plan that will guide our customers through this process. In this article, we will outline the key steps involved in creating initial comms and timelines for Airflow migration.

As a maintainer of Airflow, we want to provide a timeline and some certainty to the customer-base so that we can bring them with us on this migration journey. This is a crucial step in ensuring that our customers are aware of the changes that are coming and can plan accordingly.

To successfully migrate Airflow customers, we need to provide them with some comms and timelines to work against. This will be particularly crucial for the major monolithic pipelines, as we found with the compute migration. By providing clear communication, we can minimize the pain and disruption associated with the migration process.

While we have not received any specific responses from users, we understand the importance of having a clear communication plan in place. This will ensure that our customers have a single point of contact for any questions or concerns they may have during the migration process.

We have not identified any specific user types that require special consideration during the migration process. However, we will ensure that our communication plan is inclusive and accessible to all users.

If we migrate Airflow customers with minimal pain, then we'll be setting the community up for success. This is our hypothesis, and we believe that by providing clear communication and a well-planned timeline, we can achieve this goal.

To achieve our goal, we propose the following:

Overall Timeline/Plan: We will create a comprehensive timeline that outlines the key milestones and deadlines associated with the migration process.
Comms on Existing Repo: We will communicate to customers that the existing repo will be moved to 'Updates Only' mode and what this means for customers/data engineers reviewing PRs.
Signposting Customers: We will signpost customers to both our documentation and where they can get additional support if they need it to migrate.

To create the timeline, we will work internally to produce a comprehensive plan that outlines the key milestones and deadlines associated with the migration process. This plan will be agreed upon within the team before we share it with the wider community.

We have not received any additional information that is relevant to this proposal.

To ensure that we have successfully created initial comms and timelines for Airflow migration, we will use the following definition of done:

Comms are available to end users: We will ensure that our communication plan is available to all end users and that they are aware of the changes that are coming.
Planned disruptions or shutdowns are listed in Pagerduty: We will list any planned disruptions or shutdowns in Pagerduty to ensure that our customers are aware of any potential disruptions.
Date for 'Airflow' to move to 'Update-Only' mode is listed: We will list the date for when 'Airflow' will move to 'Update-Only' mode to ensure that our customers are aware of the changes that are coming.

Creating initial comms and timelines for Airflow migration is a crucial step in ensuring that our customers are aware of the changes that are coming and can plan accordingly. By following the proposal outlined above, we can create a comprehensive communication plan that will guide our customers through this process.
✈ Airflow - Create Initial Comms/Timelines for Airflow Migration: Q&A

In our previous article, we outlined the key steps involved in creating initial comms and timelines for Airflow migration. In this article, we will answer some of the most frequently asked questions related to this topic.

A: The purpose of creating initial comms and timelines for Airflow migration is to provide a clear plan and timeline to our customers, so that they can plan and prepare for the changes that are coming. This will help minimize the pain and disruption associated with the migration process.

A: The team responsible for creating the initial comms and timelines will work internally to produce a comprehensive plan that outlines the key milestones and deadlines associated with the migration process. This plan will be agreed upon within the team before it is shared with the wider community.

A: The key components of the initial comms and timelines include:

Overall Timeline/Plan: A comprehensive timeline that outlines the key milestones and deadlines associated with the migration process.
Comms on Existing Repo: Communication to customers that the existing repo will be moved to 'Updates Only' mode and what this means for customers/data engineers reviewing PRs.
Signposting Customers: Signposting customers to both our documentation and where they can get additional support if they need it to migrate.

A: The initial comms and timelines will be communicated to customers through a variety of channels, including:

Documentation: Our documentation will be updated to reflect the changes that are coming.
Email: Customers will receive email notifications about the changes that are coming.
Pagerduty: Any planned disruptions or shutdowns will be listed in Pagerduty to ensure that customers are aware of any potential disruptions.

A: The definition of done for creating initial comms and timelines includes:

Comms are available to end users: Our communication plan is available to all end users and they are aware of the changes that are coming.
Planned disruptions or shutdowns are listed in Pagerduty: Any planned disruptions or shutdowns are listed in Pagerduty to ensure that customers are aware of any potential disruptions.
Date for 'Airflow' to move to 'Update-Only' mode is listed: The date for when 'Airflow' will move to 'Update-Only' mode is listed to ensure that customers are aware of the changes that are coming.

A: The benefits of creating initial comms and timelines for Airflow migration include:

Minimizing disruption: By providing a clear plan and timeline, we can minimize the disruption associated with the migration process.
Ensuring customer awareness: Our customers will be aware of the changes that are coming and can plan accordingly.
Reducing support requests: By providing clear communication, we can reduce the number of support requests that we receive.