From: Steve Hancock Date: Wed, 9 Nov 2022 16:57:18 +0000 (-0800) Subject: update docs X-Git-Tag: 20221112~2 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=9c428ed979afd4315bb54a3fc9c992114c561526;p=perltidy.git update docs --- diff --git a/CHANGES.md b/CHANGES.md index d6c8bf06..cb52ceaa 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -109,7 +109,7 @@ $j -= $shell ) - This will change some existing formatting. + This will change some existing formatting with very long 'for' terms. - The following new parameters are available for manipulating trailing commas of lists. They are described in the manual. @@ -127,6 +127,10 @@ release on large files due to optimizations made with the help of Devel::NYTProf. + - This version was stress-tested for over 200 cpu hours with random + input parameters. No failures to converge, internal fault checks, + undefined variable references or other irregularities were seen. + ## 2022 06 13 - No significant bugs have been found since the last release but users diff --git a/docs/ChangeLog.html b/docs/ChangeLog.html index f6f918a4..749d9daf 100644 --- a/docs/ChangeLog.html +++ b/docs/ChangeLog.html @@ -109,7 +109,7 @@ $j -= $shell ) - This will change some existing formatting. + This will change some existing formatting with very long 'for' terms. - The following new parameters are available for manipulating trailing commas of lists. They are described in the manual. @@ -126,6 +126,10 @@ - This version runs 10 to 15 percent faster than the previous release on large files due to optimizations made with the help of Devel::NYTProf. + +- This version was stress-tested for over 200 cpu hours with random + input parameters. No failures to converge, internal fault checks, + undefined variable references or other irregularities were seen.

2022 06 13

diff --git a/local-docs/Release-Checklist.md b/local-docs/Release-Checklist.md index 9fb606bc..a08212d0 100644 --- a/local-docs/Release-Checklist.md +++ b/local-docs/Release-Checklist.md @@ -7,8 +7,8 @@ - run NYTProf and check the activity and performance of all changed code - suggested random testing minimum test duration without irregularities: - 3 cpu hours for a commit candidate - - 8 cpu hours for a +0.01 version bump candidate - - 24 cpu hours for a new release candidate + - 24 cpu hours for a +0.01 version bump candidate + - 100 cpu hours for a new release candidate - run 'author tests' on a much larger body of code than is covered by the .t files. - compare results of the current version with previous version