Feature Gate Activation Process

Follow these steps to activate a feature gate. 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. Note the precursor to these steps can be found at Feature Gate Setup Process

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

Timing

Once your feature is next on the schedule it should be activated within 1 or 2 epochs. When possible avoid forking validators and RPC nodes and avoid activating feature gates on the weekend. If you're unsure ask for guidance in #releng.

The process of activating a feature gate takes a day or two. Adjust the times mentioned in steps below to avoid weekend activations and improve Discord engagement by posting while people are awake.

1. Ensure the feature gate can be activated

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

2. Ensure the feature gate is scheduled to be activated

Refer to the Feature Gate Activation Schedule to make sure this feature gate 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

Suggested timing: 1 - 2 days before the epoch boundary

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

🚨 Feature Gate Activation 🚨 Any objections to activating this feature gate on Testnet for epoch 400, beginning approximately 1 day 2 hours from now?

Ftok4njE8b7tDffYkC5bAbCaQv5sL6jispYrprzatUwN | SPL Token Program version 3.4.0 release #24740

Template:

🚨 **Feature Gate Activation** 🚨 Any objections to activating this feature gate on *<cluster>* for epoch <next epoch>, beginning approximately <days> day(s) <hours> hour(s) from now?
<feature pubkey> | <feature description>

4. Message intent to activate in appropriate cluster channel

Suggested timing: 1 hour after posting in #releng

Channels: #mb-announcements #testnet-announcements #devnet-announcements

Template:

🚨 **Feature Gate Activation** 🚨 I am planning to activate this feature gate on *<cluster>* for epoch <next epoch>, beginning in approximately <days> day(s) <hours> hour(s). This will fork nodes not running at least <minimum version(s)>. Please see #releng for discussion.
<feature pubkey> | <feature description>

5. Schedule the feature gate for activation

Suggested timing: 12 hours before epoch boundary

Double check you are specifying the correct cluster!

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

Message in #releng and the appropriate #<cluster>-announcements that the feature gate has been activated

6. Post-activation tasks

1. Update the Feature Gate Activation Schedule
2. Update the feature Gate's PR for the activation epoch
3. In case it was the last activation of the feature, open a PR to remove its feature gating logic on master. But leave its key and description in feature_set.rs.