From 1132af2de3351ec65719c30fd5b4d6748656f710 Mon Sep 17 00:00:00 2001
From: Matthias Fasching <5011972+fasmat@users.noreply.github.com>
Date: Thu, 24 Aug 2023 08:35:41 +0000
Subject: [PATCH] Prepare v1.1.2 release (#4898)

## Motivation
Prepares a new release: v1.1.2

## Changes
- Update RELEASE.md
- After merge: rebase `v1.1` branch and tag `v1.1.2`

## Test Plan
n/a

## TODO
<!-- This section should be removed when all items are complete -->
- [x] Explain motivation or link existing issue(s)
- [x] Test changes and document test plan
- [x] Update documentation as needed

## DevOps Notes
<!-- Please uncheck these items as applicable to make DevOps aware of changes that may affect releases -->
- [x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
- [x] This PR does not affect public APIs
- [x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
- [x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)
---
 CHANGELOG.md |  3 ++-
 RELEASE.md   | 16 ++++++++++++++++
 2 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 233a0f2363..ff6f31fa47 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,7 +2,7 @@
 
 See [RELEASE](./RELEASE.md) for workflow instructions.
 
-## UNRELEASED
+## v1.1.2
 
 ### Upgrade information
 
@@ -65,3 +65,4 @@ Doesn't affect direct peers. In order to disable:
 
 * [#4882](https://github.com/spacemeshos/go-spacemesh/pull/4882) Increase cache size and parametrize datastore.
 * [#4887](https://github.com/spacemeshos/go-spacemesh/pull/4887) Fixed crashes on API call.
+* [#4871](https://github.com/spacemeshos/go-spacemesh/pull/4871) Add jitter to spread out requests to get poet proof and submit challenge
diff --git a/RELEASE.md b/RELEASE.md
index 7e747f5bca..713ef58c18 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -23,3 +23,19 @@ Cherry-pick selected commits to major release branch.
 Copy selected commits to CHANGELOG.md.
 Rename UNRELEASED to a concrete <version>.
 Commit changes, and create a tag.
+
+## Preparing for next release
+
+After releasing a new major or minor version, create a new UNRELEASED section at the top of CHANGELOG.md:
+
+```markdown
+## UNRELEASED
+
+### Upgrade information
+
+### Highlights
+
+### Features
+
+### Improvements
+```