diff options
| author | dana <dana@dana.is> | 2019-01-04 08:38:15 -0600 |
|---|---|---|
| committer | dana <dana@dana.is> | 2019-01-04 08:38:15 -0600 |
| commit | f5c096fea7deba2853198da4746063360f26c7c3 (patch) | |
| tree | d518271d46ab45924f4e1734fd56370e5fe61674 /Etc | |
| parent | 232b43571f8ffda16889686a7aeffd4d9a386386 (diff) | |
| download | zsh-f5c096fea7deba2853198da4746063360f26c7c3.tar.gz zsh-f5c096fea7deba2853198da4746063360f26c7c3.tar.xz zsh-f5c096fea7deba2853198da4746063360f26c7c3.zip | |
43970: Update NEWS for previously unmentioned features in 5.{4,5,6}
Also clarify release documentation and fix a typo mentioned in workers/43971
Diffstat (limited to 'Etc')
| -rw-r--r-- | Etc/creating-a-release.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt index 2445151f5..fd52da86a 100644 --- a/Etc/creating-a-release.txt +++ b/Etc/creating-a-release.txt @@ -11,6 +11,10 @@ To create a zsh release: README NEWS + README should document compatibility-breaking changes. Generally, NEWS should + document new features and major bug fixes (but not routine fixes or changes to + completion/contrib functions). + - Commit those changes with an "unposted" ChangeLog entry. git commit -am "Test release: 5.5.1-test-1." && |