John Safranek
83152c767f
touch dates
2020-04-21 10:50:59 -07:00
John Safranek
7b6cc2056b
Update release date in readme and changelog.
2020-04-21 10:21:59 -07:00
John Safranek
c134626946
Update credit names on vuln notice in README.
2020-04-21 10:21:59 -07:00
John Safranek
a29eac035b
Update credit for vulnerability report.
2020-04-21 10:21:58 -07:00
John Safranek
836e77508d
Remove notes for reverted DTLS commits.
2020-04-21 10:21:58 -07:00
John Safranek
e84cd1a887
Updated the README file and ChangeLog for some spelling and omissions.
2020-04-21 10:21:58 -07:00
John Safranek
27011ff7ff
Release Rollup
...
1. Update configure with the new version.
2. Update the ChangeLog.
3. Update the readme.
2020-04-21 10:21:53 -07:00
David Garske
3df9ca3fae
Fix to use TBD version for next release.
2020-01-30 06:26:45 -08:00
David Garske
6cf63b1738
Template for ChangeLog.md for next release. New PR's should update this document if its worth mention in the change log.
2020-01-30 06:26:45 -08:00
kaleb-himes
9b8d4e91c2
Fixing some typos. Thanks to Fossies for the report
2020-01-10 11:45:51 -07:00
Jacob Barthelmeh
5675a2b3c5
prepare for release v4.3.0
2019-12-20 08:43:34 -07:00
Jacob Barthelmeh
1cbc2536cc
prepare for release version 4.2.0
2019-10-21 16:32:41 -06:00
Jacob Barthelmeh
77fda069a8
prepare for release version 4.1.0
2019-07-23 09:27:39 -06:00
John Safranek
1c237af5b3
Release Fixes
...
1. Update the date in README and ChangeLog to today.
2019-03-20 11:08:10 -07:00
John Safranek
ce4b54944b
Updates for v4.0.0
...
Updated the README files and ChangeLog.
2019-03-15 09:42:45 -07:00
Jacob Barthelmeh
b6d61f2987
prepare for release 3.15.7
2018-12-23 22:18:48 -07:00
Jacob Barthelmeh
cd37e3967c
prepare for release 3.15.5
2018-11-07 16:08:29 -07:00
Jacob Barthelmeh
8fd18e06f7
prepare for release v3.15.3
2018-06-21 12:22:27 -06:00
Tim Parrish
9448b96afd
updated change log
2018-06-12 14:15:57 -06:00
John Safranek
1c17f55ee4
updated the readme/changelog with the correct release date
2018-06-05 16:10:08 -07:00
John Safranek
0c966d7700
Update ChangeLog and NEWS
...
While the GNU coding standard states that the NEWS file should be a list of the high level changes and the ChangeLog should be every change in detail, our public source repository contains the detailed log of all changes and the name "ChangeLog" makes more sense to me than "NEWS". Instead of keeping two copies of the README, one in plain text and one in MarkDown, only keeping the MarkDown copy. It displays better in the source repository, it is still plain text, and we aren't keeping two separate copies of the files.
2018-06-05 16:07:53 -07:00