I was thinking of starting with something like this:
https://github.com/skywinder/github-changelog-generator#output-example.
I will also look at the github-changes that Steve mentions.
Hank
On 10/26/2017 08:48 AM, Steve Malenfant wrote:
Do we have a sample from a script that would create a change log based on
pull request only? I tried `github-changes` yesterday but it seemed to work
only with the older releases (<1.8). Although I haven't spent much time on
it.
We should probably only list the high level changes such as new features,
improvements, important fixes and breaking changes (relates to operations
action required).
Few things we should note as well :
- How to upgrade from pre-2.0 releases
- What are the upgrade procedures (run postinstall for example)
- Profiles locations (not included in 2.x basic install anymore)
I'm sure some of those are documented already, might just requires
references.
Steve
On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty <[email protected]> wrote:
Hello Steve,
The release notes are still being worked on. I am also looking for
suggestions on how the release notes should be formatted, and how they
might be auto-generated. If you have any, please let me know.
Regards,
Hank
On 10/24/2017 07:26 AM, Steve Malenfant wrote:
Is there any Release Notes associated with this release? 1,337 changes and
the link above will only display 250 of them.
Steve
On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <[email protected]> wrote:
Hello All,
I've prepared a release for v2.1.0-RC1
The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.
[ ] +1 Approve the release
[ ] -1 Do not release this package because ...
Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC1
This corresponds to git:
Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <(505)%20927-1206>
<(505)%20927-1206>
Tag: RELEASE-2.1.0-RC1
Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1
My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get&search=0x582D3F6E79270895
Make sure you refresh from a key server to get all relevant signatures.
The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcont
rol/2.1.0/RC1
Thanks!
