Talk:Release notes/Flow

Previous page history was archived for backup purposes at Talk:Release notes/LQT Archive 1 on 2015-07-10.

I think mw-json HTML tables are a useful feature, but there seems to be no mention of it in the changelog.

Does anyone know when it was introduced so we can add it? And did the JSON content model exist before mw-json HTML tables were introduced?

Proper JSON support was brought into core in d2a82fcb604 which first shipped in MediaWiki 1.24.0 (it earlier sat in an extension). The JSON content model constant CONTENT_MODEL_JSON was created as part of that patch.

format

(please correct in case of misconceptions)

At the moment, there are the wmf/1.35.0-wmf.3, the REL1_34 and the master branch. 1.33 (stable) is released, 1.34 (beta) isn't yet. 1.35 is marked as alpha, git master.

• REL1_34 - contains commits not in 1.33 that will be part of the 1.34 release(, if not reverted).
• master - contains commits not in 1.33 that will be part of the 1.35 release(, if not reverted). Most, if not all commits in REL1_34 are also in master. On the other hand, a (project manager|developer) could decide that a feature should not be part of 1.34 so you find the commit only in master (and not in REL1_34). Those features will become part of 1.35 -- at some point in the future the REL1_35 branch is created from master.
• wmf/1.35.0-wmf.\d - "Release" branches for the Wikimedia Wikis. While 1.34 isn't released, the Wikimedia Wikis receive changes from the master branch (1.35). There exist 3 groups of Wikis: The most less important always get the newest (highest) branch first (test.*, mediawiki.org) and the most important ones (en.wp) last. Having these branches helps applying "emergency" fixes and running Wikis with different Versions.

The confusing bit now is the definition of Date branched from master. For MediaWiki 1.34, is it the date the REL1_34 was created - REL1_34 may potentially start to contain different commits than master - or the date REL1_35 will be created - when REL1_34 will only receive bug fixes?

Theoretically it's already in that state (rc.0 having been released), but that's at the judgement call of people who are supporting particular features, who may choose to backport them (or supporting commits) to make transition easier for sysadmins using MediaWiki.

Hi all, The 'Git' links of the page built with 'phabricator.wikimedia.org' start today with release 1.23 as the oldest. And these Git links to previous release notes lead to empty pages. Ex:

https://phabricator.wikimedia.org//r/p/mediawiki/core;browse/REL1_22/RELEASE-NOTES-1.22

With a magic trick I can reach the release note 1.18 but built with 'gerrit.wikimedia.org'

https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/1.18.6/RELEASE-NOTES-1.18

Can somebody update the page such as to always access the real Release Note of the versions where ever they are ? Thank you.

Christian Wia (talk) 17:26, 16 June 2019 (UTC)

This is thread is not specifically about this page, but about the many subpages it has (one for each X.Y release; e.g., Release notes/1.22). It would be helpful to include in each version section the date that it was originally released.

I aggree it would be an interesting information on these pages. I just collected some data about the releases, so now these informations can be found in a central page, although this page is a bit heavy and difficult to read; and they could be used to write down the important dates on the release notes pages.

comores

Release notes are duplicated across e.g. MediaWiki 1.28 and Release notes/1.28.

Expectedly, this leads to desynchronization and outdating.