Feature Activation Process

Follow these steps to activate a feature. This process is to ensure communication and coordination happens, so node operators/developer/engineers are not blindsided. The specific CLI commands and args are mostly left out on purpose, as learning how to use the CLI is not the goal of this doc; if you are unsure of the commands, seek help before proceeding.

Please check back here before each activation, as this checklist will be updated.

1. Ensure the feature can be activated

Run solana feature status -u[tdm] to see if feature activation is allowed for the required version. Note, this does not consider --yolo.

2. Ensure the feature is scheduled to be activated

Refer to the Feature Activation Schedule to make sure this feature is next to be activated. If not, do not proceed without further coordination in #releng on the Solana Discord.

3. Message intent-to-activate in #releng

Message that you intend to activate a feature. Specify the cluster (i.e. Testnet, Devnet, Mainnet-beta), and the feature name/description. For example:

🚨 Feature Activation 🚨 Any objections to activating this feature on Testnet?

Ftok4njE8b7tDffYkC5bAbCaQv5sL6jispYrprzatUwN | SPL Token Program version 3.4.0 release #24740

🙋 TODO: How much time before the next epoch should this message happen?

🙋 TODO: How much time should you wait before activating?

4. Activate the feature

Double check you are specifying the correct cluster!

Perform the feature activation. Plan to be available and around at the next epoch boundary to ensure the activation goes smoothly.

5. Post-activation tasks

1. Message in #releng that the feature has been activated
2. Update the Feature Activation Schedule
3. Update the feature's PR for the activation epoch

🙋 TODO: Should there be an announcement in the cluster-specific Discord channel?