mirror/json-c
1
0
Fork 0
mirror of https://github.com/json-c/json-c.git synced 2026-03-29 01:49:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fill in a few more pre-release steps to match what we've done for the 0.14 release.

Browse Source 
Move the list of contributors to the AUTHORS file.
This commit is contained in:
Eric Haszlakiewicz
2020-04-19 01:28:24 +00:00
parent 4badbe9c20
commit 9ed00a694b
3 changed files with 55 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
AUTHORS
View File

@@ -1,4 +1,30 @@
Michael Clark <michael@metaparadigm.com> Alexander Dahl <post@lespocky.de>
Jehiah Czebotar <jehiah@gmail.com> andy5995 <andy400-dev@yahoo.com>
Eric Haszlakiewicz <hawicz+json-c@gmail.com> Björn Esser <besser82@fedoraproject.org>
changyong guo <guo1487@163.com>
chenguoping <chenguopingdota@163.com>
Christopher Head <chead@chead.ca>
Chris Wolfe <chriswwolfe@gmail.com>
C. Watford (christopher.watford@gmail.com) C. Watford (christopher.watford@gmail.com)
Darjan Krijan <darjan_krijan@gmx.de>
Eric Hawicz <erh+git@nimenees.com>
grdowns <grdowns@microsoft.com>
Ivan Romanov <drizt@land.ru>
Jaap Keuter <jaap.keuter@xs4all.nl>
janczer <menshikov.ivn@gmail.com>
Jehan <jehan@girinstud.io>
Jehiah Czebotar <jehiah@gmail.com>
Jonathan Wiens <j.wiens@teles.com>
Jose Bollo <jose.bollo@iot.bzh>
Keith Holman <keith.holman@windriver.com>
Liang, Gao <liang.gao@intel.com>
max <mpano91@gmail.com>
Michael Clark <michael@metaparadigm.com>
myd7349 <myd7349@gmail.com>
Pierce Lopez <pierce.lopez@gmail.com>
Po-Chuan Hsieh <sunpoet@sunpoet.net>
Ramiro Polla <ramiro.polla@gmail.com>
Rikard Falkeborn <rikard.falkeborn@gmail.com>
Robert <roby_p97@yahoo.com>
Rubasri Kalidas <rubasri.kalidas@intel.com>
Unmanned Player <36690541+unmanned-player@users.noreply.github.com>

30
ChangeLog
View File

@@ -12,36 +12,6 @@ Deprecated and removed features:
Build changes: Build changes:
-------------- --------------
Contributors to this release
----------------------------
* Alexander Dahl <post@lespocky.de>
* andy5995 <andy400-dev@yahoo.com>
* Björn Esser <besser82@fedoraproject.org>
* changyong guo <guo1487@163.com>
* chenguoping <chenguopingdota@163.com>
* Christopher Head <chead@chead.ca>
* Chris Wolfe <chriswwolfe@gmail.com>
* Darjan Krijan <darjan_krijan@gmx.de>
* Eric Hawicz <erh+git@nimenees.com>
* grdowns <grdowns@microsoft.com>
* Ivan Romanov <drizt@land.ru>
* Jaap Keuter <jaap.keuter@xs4all.nl>
* janczer <menshikov.ivn@gmail.com>
* Jehan <jehan@girinstud.io>
* Jonathan Wiens <j.wiens@teles.com>
* Jose Bollo <jose.bollo@iot.bzh>
* Keith Holman <keith.holman@windriver.com>
* Liang, Gao <liang.gao@intel.com>
* max <mpano91@gmail.com>
* myd7349 <myd7349@gmail.com>
* Pierce Lopez <pierce.lopez@gmail.com>
* Po-Chuan Hsieh <sunpoet@sunpoet.net>
* Ramiro Polla <ramiro.polla@gmail.com>
* Rikard Falkeborn <rikard.falkeborn@gmail.com>
* Robert <roby_p97@yahoo.com>
* Rubasri Kalidas <rubasri.kalidas@intel.com>
* Unmanned Player <36690541+unmanned-player@users.noreply.github.com>
0.13.1 (up to commit 0f814e5, 2018/03/04) 0.13.1 (up to commit 0f814e5, 2018/03/04)
========================================= =========================================

41
RELEASE_CHECKLIST.txt
View File

@@ -1,23 +1,34 @@
Release checklist: # Release checklist:
Figure out whether a release is worthwhile to do. ## Pre-release tasks
Analyze the previous release branch to see if anything should have beeni
* Figure out whether a release is worthwhile to do.
* Analyze the previous release branch to see if anything should have been
applied to master. applied to master.
Analyze APIs between previous release branch and master to produce list of * Collect changes and assemble tentative release notes.
changes (added/removed/updated funcs, etc...), and detect backwards compat * Identify previous release branch point
issues. * Check commit logs between previous branch point and now for
If the new release is not backwards compatible, then this is a MAJOR release. notable changes worth mentioning
Collect changes and assemble tentative release notes. * Create a new issues_closed_for_X.Y.md file
Identify previous release branch point * Include notable entries from here in the release notes.
Check commit logs between previous branch point and now * Analyze APIs between previous release branch and master to produce list of
Create a new issues_closed_for_X.Y.md file changes (added/removed/updated funcs, etc...), and detect backwards compat
issues.
* https://github.com/lvc/abi-compliance-checker
* If the new release is not backwards compatible, then this is a MAJOR release.
* Mention removed features in ChangeLog
* Update the AUTHORS file
* Exclude mentioning changes that have already been included in a point
release of the previous release branch.
Update ChangeLog with relevant notes before branching. * Update ChangeLog with relevant notes before branching.
Check that the compile works on Linux * Check that the compile works on Linux - automatic through Travis
Check that the compile works on NetBSD * Check that the compile works on NetBSD
Check that the compile works on Windows * Check that the compile works on Windows - automatic through AppVeyor
## Release creation
Start creating the new release: Start creating the new release:
release=0.14 release=0.14