ditch CHANGELOG.md in favor of github releases

[ahmadnassri]

maintaining a single markdown file will get lengthy and harder as you add more releases.

Github Releases, not only shows the appropriate release names / tag / assets, but is also Markdown powered, so you end up with a better "change log" that's also paginated, with direct links to versioned tag + release assets.

[thibaultcha]

I prefer a change log.

[ahmadnassri]

can we at least update the release description in Github Releases with meaningful info?

[thibaultcha]

you can do it if you want but I think it'll be useless.

A changelog is:

• more flexible
• less relying on github
• easier to search in
• part of the git history

From there, I see no reason to write things in releases or to duplicate information between the two. Except for a link to the changelog section.

[nijikokun]

Generally projects do both, so, in the famous words of zoidberg, "why not both?"

By doing releases, you add your changelog message there, which you can then copy it over to changelog.md. Or vice versa.

[ahmadnassri]

thinking of github releases as simple/unified way that we can always rely on finding the info across all our projects, oss or not, regardless of the source (CHANGELOG.md, JIRA, git history)

give us a consistent way to find the info across many projects rather than remembering different wikis / source control.

plus its API accessible, so that's neat

[thibaultcha]

We'll update release notes. let's stop nitpicking