Updating the Download wiki page status for 5.1.6 (Homebrew & Linux)

Development
4

@Nick-Hall This is a good point. Could you add to your What to do for a release to include a Message to package maintainers to ensure the Gramps Downloads page is updated after a new package is posted?
It might suggest either:

  1. email the developers maillist when the package is updated
  2. update the appropriate Version template on the Wiki

We have to use MediWiki’s transclusion templates for the Version numbers because there are so many translations of the Gramps Downloads wiki page. The drawback to this is that MediaWiki templates add another layer of markdown specialized knowledge to assimilate. (Our project has a lot of different markdown dialects to learn: the internal Gramps Notes, GitHub, Discourse, MediaWiki, MantisBT, HTML, Python text styling) So it makes sense to just send an eMail and let the WikiContributors handle that piece of announcement.

Note that some package maintainers are preparing for the proverbial bus by documenting their process for a release. It also serves as a checklist when the process becomes too convoluted to remember easily. (See the wiki articles for a New Gramps Release, an AIO installer, rolling over a new Wiki manual version)

We are slowly adding standard hints to the Templates for the MediaWiki template too. (Since they are updated so infrequently that WikiContributors forget too.) The format is still evolving. See the templates for the Stable branch and version of the wiki manual

We have a predictable cluster of new releases right now. (5.1.6 was just released, the 5.2 beta is imminent, the 5.2 public release will follow shortly.)

So now is an opportune time for package maintainers to build a checklist for the packages without any ‘bus insurance’. And for those who have a WikiContributor account, they can begin to build such a checklist on their personal page. (WikiContributors can also edit your personal MediaWiki Watchlist so that they will be notified of future changes to the template for the package being maintained.) And you can send an eMail on the developer mailist if you want help converting a checklist to a public article.