Add a folder to track CHANGELOG entries for the next release 2022-08-announcement-rework
authorMatt Corallo <git@bluematt.me>
Wed, 7 Sep 2022 00:01:12 +0000 (00:01 +0000)
committerMatt Corallo <git@bluematt.me>
Thu, 8 Sep 2022 19:50:36 +0000 (19:50 +0000)
CONTRIBUTING.md
pending_changelog/1699.txt [new file with mode: 0644]

index f7cf8c4e699e3578285abbdbe3c72b8a0f06759b..f1e4ce5171e71626f124701741e4f485a96f9ad5 100644 (file)
@@ -100,6 +100,10 @@ comment suggesting that you're working on it. If someone is already assigned,
 don't hesitate to ask if the assigned party or previous commenters are still
 working on it if it has been awhile.
 
+Any changes that have nontrivial backwards compatibility considerations should
+have an entry added in the `pending_changelog` folder which includes the
+CHANGELOG entries that should be added in the next release.
+
 Peer review
 -----------
 
diff --git a/pending_changelog/1699.txt b/pending_changelog/1699.txt
new file mode 100644 (file)
index 0000000..75ed45d
--- /dev/null
@@ -0,0 +1,2 @@
+`broadcast_node_announcement` has been moved to `PeerManager` from `ChannelManager`.
+`PeerManager::new`'s new `current_time` argument must be set to a UNIX timestamp, not a persistent counter, for any existing nodes that upgrade.