From 8a99d2d56fc53e3e8c0508631d372fa64c13911b Mon Sep 17 00:00:00 2001 From: Mathieu Hofman <86499+mhofman@users.noreply.github.com> Date: Mon, 16 Sep 2024 20:25:43 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Richard Gibson --- MAINTAINERS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 3b11c5c3a1f..82c424881cb 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -10,11 +10,11 @@ We would like to have similar behavior regardless of whether a chain launched fr We previously maintained `release-*` branches which represented a fork of the `master` dev branch at a given point: - `release-pismo` is the original/archived release branch used before the "bulldozer" upgrade which threw away all JavaScript state. -- `release-mainnet1B` was our previous release branch up until upgrade-15. Despite its name, it lived beyond the "mainnet-1" phase of the agoric-3 chain. +- `release-mainnet1B` was our previous release branch up until `agoric-upgrade-15`. Despite its name, it lived beyond the "mainnet-1" phase of the agoric-3 chain. We don't expect these previous release branches to ever be updated again. -Starting with `upgrade-16`, we try to release directly from `master` by creating a `dev-release-*` branch. These branches allow us to work on the release concurrently with other engineering efforts, and are not currently merged back once the release is complete. +Starting with `agoric-upgrade-16`, we try to release directly from `master` by creating a `dev-release-*` release branch. These branches allow us to work on the release concurrently with other engineering efforts, and are not currently merged back once the release is complete. Releases are tagged commits from the above release branches, with a corresponding entry in https://github.com/Agoric/agoric-sdk/releases .