Mention that changes in 3.2.x should also be part of 3.3.0
It's a bit wasteful to also mention these changes in the Git notes, so don't do it and just leave a reminder to copy the existing change log entries from 3.2 branch instead when it's time to release 3.3.0.
This commit is contained in:
parent
5b89e53bc3
commit
541be26e78
1 changed files with 4 additions and 0 deletions
|
|
@ -18,6 +18,10 @@ Changes in behaviour which may result in build errors
|
|||
3.3.0: (released 2022-??-??)
|
||||
----------------------------
|
||||
|
||||
NOTE: In addition to the note below, also incorporate (either by
|
||||
copy or by reference) all the changes in the 3.2 branch (i.e.
|
||||
everything in this file after 3.2.0 in that branch).
|
||||
|
||||
NOTE: This file is updated only before the release, please use
|
||||
|
||||
$ git log --notes=changelog --format='%N' v3.2.0..|grep .
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue