Fetch release note dates from metadata

[andrewnicols]

As requested in #298.

This issue introduces a new React component:

<ReleaseNoteIntro releaseName="4.0.2" />

This will display the:

• release date
• link to the tracker

I've also updated the page description for the meta tag because the import statement and React tags mess with it.

[netlify]

✅ Deploy Preview for moodledevdocs ready!

Name	Link
🔨 Latest commit	a9678ed
🔍 Latest deploy log	https://app.netlify.com/sites/moodledevdocs/deploys/62cd6d36b11bab000935d810
😎 Deploy Preview	https://deploy-preview-300--moodledevdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 87	🟢 98	🟢 100	🟢 90	🟢 100	Report
/docs/apis/commonfiles	🟠 69	🟢 96	🟢 100	🟢 100	🟢 100	Report
/general/development/gettingstarted	🟢 91	🟢 96	🟢 100	🟢 90	🟢 100	Report
/general/releases	🟠 84	🟢 96	🟢 100	🟢 100	🟢 100	Report

[stronk7]

Couple of comments:

1. I imagine those return null when a given release is not found means, in practice, print nothing, correct?
2. Following on the previous point, could make sense (just asking!) to add the Release date: to be released + the link to the list of issues instead of printing nothing?

It looks great, I don't quite understand how those helpers work, but I'm sure you do, super Andrew!

Ciao :-)

[andrewnicols]

1. I imagine those return null when a given release is not found means, in practice, print nothing, correct?

Correct - it's known as conditional rendering. You can read more about it here:
https://reactjs.org/docs/conditional-rendering.html#preventing-component-from-rendering

2. Following on the previous point, could make sense (just asking!) to add the Release date: to be released + the link to the list of issues instead of printing nothing?

We can do that :)

We already collect information about versions which aren't yet released - it's something we need to add to https://moodledev.io/general/development/process/release - I notice that it's not a current step for the current list of releases. When we add the new doc page for the next release, we should also be adding the versions.json entry.

I've created #302 - which I thought I had already created but hohum. That's to create a script to update the versions.json file and the skeleton for the next version.

It looks great, I don't quite understand how those helpers work, but I'm sure you do, super Andrew!

[sarjona]

Thanks for working on this, Andrew! It's great to keep adding this king of automatisation to the devdocs!! <3

[stronk7]

Yay, well done! 🎈