create_release_notes.sh include .adoc files

[Josh Stompro]

The create_release_notes.sh script under /docs/RELEASE_NOTES_NEXT looks like it limits to gathering *.txt files in a few locations. Since DIG is looking to move to using the .adoc extension, that script needs to be updated to handle both *.txt and *.adoc.

It outputs a .txt file also, which will probably need to be changed to .adoc for consistency. Maybe the first step should just be to support sections written with the .adoc format.

http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=docs/RELEASE_NOTES_NEXT/create_release_notes.sh;h=47d6e7ddb11632ebd1dd7b9415e26d3049a109f9;hb=HEAD

Josh

[Josh Stompro (u-launchpad-stompro-org)]

user/stompro/lp1482336_adoc_release_notes

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1482336_adoc_release_notes

Branch that adds adoc as a valid extension for release notes, also changes release notes output to .adoc.

Josh

[Jason Stephenson (jstephenson)]

Question: Why use .adoc, when most other projects/places that use asciidoc for documentation use .asciidoc?

[Dan Scott (denials)]

Because .adoc is shorter, recognized and rendered by Github, and DIG would like to use it.

[Jason Stephenson (jstephenson)]

All right. I didn't realize that GitHub recognized also recognized .adoc. Seeing .asciidoc on a couple of GitHub projects is what prompted me to ask.

[Galen Charlton (gmc)]

After speaking with Yamil, I've pushed this to master, along with a follow-up changing the extension of the release note template and existing release notes snippets in master. Thanks, Josh!