-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GitHub Release notes #4807
Comments
To clarify: I'm aware this move was haphazard, not coordinated, and I haven't contributed to cabal in ages. I also think the new release notes are a strict improvement, they would have helped past me, and they're likely to help others. |
Forgot to say: this was after I failed finding good such release notes for ~30 minutes.
Some of that time was also spent on http://www.haskell.org/, https://wiki.haskell.org/Haskell, googling for "haskell cabal news 2" or such, looking at |
np, I guess that updating the GitHub releases page should be added to release checklist.
I just checked, and my blog post comes up as one of the top hits when you google for "cabal 2.0", however it may be just me. I'll add a couple more links. |
I had searched "cabal 2.0 news", which has pretty confusing results (including videogames?). Your blog is the 7th for me, which is probably why I missed it. I've seen issues on SEO for Haskell websites elsewhere, but I only understand "an expert could improve things and I'm not". Here's a screenshot of my results. It also doubles as "where the list might be added". EDIT:
👍 |
Well, I managed to google this issue by "cabal 2.0 release notes" :) |
I've been looking for Cabal 2 release notes in a few places. Turns out I can edit release notes for releases, so I took the liberty of adding links to @23Skidoo's post (http://coldwa.st/e/blog/2017-09-09-Cabal-2-0.html) to a couple of places:
https://github.com/haskell/cabal/releases/tag/Cabal-v2.0.0.2
https://github.com/haskell/cabal/releases/tag/cabal-install-v2.0.0.0
Unfortunately, I realized GitHub changed the release date and tagged me as releaser—I think that's unfortunate but hopefully not crucial. @23Skidoo was the original releaser—I imagine you might want to edit descriptions further.
I've already seen #4013, but a changelog belongs also on GitHub.
The text was updated successfully, but these errors were encountered: