Closed hzeller closed 3 months ago
Fair enough, maybe just a link at that commit highlighting the range of the NEWS section ?
It serves two purposes: it is possible to see the NEWS
directly (while in the assets, the browser just downloads the file), and it makes it discoverable for folks to find where it is.
So, adding a link like this:
https://github.com/avrdudes/avr-libc/blob/16b742119eaed8d966929033b1ad325faea89798/NEWS#L1-L179
... will show up as
https://github.com/avrdudes/avr-libc/blob/16b742119eaed8d966929033b1ad325faea89798/NEWS#L1-L179
Fair enough, maybe just a link at that commit highlighting the range of the NEWS section ?
Thanks for the idea, that indeed looks good!
One final nit: Would be nice to go from the github.io page directly to the code page. Currently, you have to github.io -> releases -> code.
The backlink is at the bottom of the Github.io page.
The nongnu page still points to older versions. And nongnu is still spit out by search engines. Maybe that could be adjusted, too?
https://www.nongnu.org/avr-libc/ https://www.nongnu.org/avr-libc/user-manual/index.html
Notice the link to the documentation is to the "latest" as it doesn't have the version in the URL.
I added a headline that indicates the move to Github.
I also added a 00README
file to the downloads area.
Given that the last commit hinted that 2.2.0 is around the corner, but has been sitting there for a few months, I would like to request to create a new release.
Reason is that I'd like to use the avrxmega3 (attiny1604, attiny804,...) class of devices that have been added after the last release.
If this gets a proper 2.2.0 label and release, it is much easier to convince distributions to pick up and package this version.
Thank you!
(Currently some distributions are stuck in even older versions, but that is a different story)