On Wed, Jan 6, 2021, at 19:38, Ricardo Signes wrote: > 1. We make a directory in the repo called *upgrading*. > 2. In that directory, we make a directory called *next*. > 3. Feature branches are expected to add a file to upgrading/next that > explains their upgrade requirements. > 4. When v3.x.0 is being prepared, the release manager consolidates all the > upgrading/next/* files into upgrading/v3.x.0
Having had a Cyrus call and a chat with ellie since this email, the final resolution is: * we call it "changes" and not "upgrading" * we appreciate entries that say "this branch introduced no changes" because they will save time when compiling the final document * they should include not just "how to upgrade" but whatever unstructured (but clear!) notes should be reflected in the final release notes -- Ricardo Signes (rjbs) CTO, Fastmail ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/Taa08486771d9b334-M21348ce57cfbc795ebcfb3b9 Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
