Add a release notes link to textpattern_update_available; add release notes to .com
#307
Comments
|
Actually, yeah, is it worth having a /release-notes section on .com as a long-tail archive of everything that's been done? Easy to set up with a bunch of articles in that section, each of which lists the relevant bit taken from HISTORY.txt? The landing page lists all articles. It's just a little grunt work to add a section, go through the history file and copy/paste each chunk into a new article and set the article's publish date to the release date. A quick win for SEO and for a link from this |
|
I was thinking of something very similar - a release notes landing page and then a link over to |
|
Ah right, okay so you were thinking of a single release notes page containing a link to the repo's HISTORY.txt. That would also work. Doesn't have the SEO 'refreshability look at me' but less potential work so I'm easy however way we slice it. A landing page endpoint for the gTxt string is the main goal. Anything else is icing sugar. EDIT: presumably if we link to a file in a repo on the 'main' branch, that always stays valid and points to the 'current' state of affairs, even when we tinker with it and push new commits afterwards? Just trying to avoid having to update the link each time we merge a release to the |
|
There's a risk of duplicated content if we're copying And we could have a sticky article with "here's the current stuff" + a link, then dated articles with chunks from the respective release. I prefer your idea, thinking on it. |
|
Landing page is now set ( Edit: I've started processing releases, oldest first. We can figure out styling etc when the content is in. Edit: I've cribbed the blog page and tweaked for release notes (inc metadata), perhaps we could offer an article list instead of the excerpt? It'd look tidier and be more easily reference-able. |
|
To tidy up and format, set to 'pending' for review, audit with fresh eyes (@petecooper & @Bloke):
Other stuff:
|
petecooper
changed the title
textpattern_update_availabletextpattern_update_available; add release notes to .com
|
I'd like to bump this to 4.8.8 GA milestone if that's doable. If we leave it for 4.9 then it'll be at least 4.9.1 before anyone sees it. This means we need to get the bulk of the release notes articles processed by - say - end of January, along with the landing page presentation scaffold tweaks (maybe a @philwareham gig?), and tweak the (We could change the |
|
What is the status on this? Thanks. |
Currently, we have (
en):Since this gets eyeballs, we have another opportunity to prevent someone blundering through an upgrade if they don't reach the minimum ride height. Something like:
Throw in a link to the release notes (prettied up as a page on .com?), perhaps a note for non-English languages that the release notes are in English, and I reckon that'll do it.
The text was updated successfully, but these errors were encountered: