Page MenuHomePhabricator

Release version 0.1.13
Closed, ResolvedPublic3 Estimated Story Points

Description

  1. Make a patch with subject "Release version 0.1.13".
    1. Update CHANGES.md following the instructions under "On release".
    2. Add any relevant information to the commit message.
    3. If the new version is greater than the snapshot: replace all @since tags for the new version with the correct one.
    4. Check that we haven't missed any @since tags that should be added or changed. To get all @since tags added from last version that have the wrong version number use this command, ex: git diff 0.1.12 | grep -P "^\+\s+\* @since 0\.1\.1[^1]"
    5. Check if any UI messages used for error audio (e.g. wikispeech-error-loading-audio-message) have changed. If so, regenerate corresponding audio files.
  2. Make a tag for the new version:
    1. git tag v0.1.13
    2. git push --tags
  3. Update mw:Extension:Wikispeech
    • Change the download link for the latest version under Installation.
  4. Update mw:Help:Extension:Wikispeech
  5. Create a new task for next release. Copy the description of this one to get the correct formatting. Don't forget to change version number.
  6. Update Wikispeech to latest version on VPSCloud (producer & demo wiki)

Relevant tasks

Issues

Updating producer

Details

Related Changes in Gerrit:

Event Timeline

The UI is broken when using the gadget module (see error below). This means that the settings button isn't added to the player. There may be more issues.

I would suspect that this happened in T402001: Use classes in frontend. It removed the component objects from mw.wikispeech.

I'll try to fix this in T277733: Use package files for loading modules. It's related to that. We shouldn't make a new release until it's fixed.

Page load

13:27:02.630 TypeError: can't access property "ready", mw.wikispeech.ui is undefined
    js ext.wikispeech.gadget.js:208
    jQuery 3
    using mediawiki.base.js:873
    doPropagation startup.js:769
    requestIdleCallback handler*setAndPropagate startup.js:826
    markModuleReady startup.js:1246
    runScript startup.js:1292
    cssHandle startup.js:1356
    flushCssBuffer startup.js:602
    addEmbeddedCSS startup.js:633
    execute startup.js:1370
    doPropagation startup.js:753
    requestIdleCallback handler*setAndPropagate startup.js:826
    impl startup.js:2015
    <anonymous> load.php:1
startup.js:344:9

The UI is broken when using the gadget module (see error below). This means that the settings button isn't added to the player. There may be more issues.

I would suspect that this happened in T402001: Use classes in frontend. It removed the component objects from mw.wikispeech.

I'll try to fix this in T277733: Use package files for loading modules. It's related to that. We shouldn't make a new release until it's fixed.

Page load

13:27:02.630 TypeError: can't access property "ready", mw.wikispeech.ui is undefined
    js ext.wikispeech.gadget.js:208
    jQuery 3
    using mediawiki.base.js:873
    doPropagation startup.js:769
    requestIdleCallback handler*setAndPropagate startup.js:826
    markModuleReady startup.js:1246
    runScript startup.js:1292
    cssHandle startup.js:1356
    flushCssBuffer startup.js:602
    addEmbeddedCSS startup.js:633
    execute startup.js:1370
    doPropagation startup.js:753
    requestIdleCallback handler*setAndPropagate startup.js:826
    impl startup.js:2015
    <anonymous> load.php:1
startup.js:344:9

Oh, okay, that's unfortunate, let me know if I can do something as well!

Change #1203378 had a related patch set uploaded (by Viktoria Hillerud WMSE; author: Viktoria Hillerud WMSE):

[mediawiki/extensions/Wikispeech@master] Release version 0.1.13

https://gerrit.wikimedia.org/r/1203378

Regarding this new help image, it struck me that we will likely have to change it again when this: T406016 is done, since it will change the help, feedback and edit button:

image.png (440×973 px, 66 KB)

So my question is if I should wait for that task to be merged before I update the help image?

@Sebastian_Berlin-WMSE Regarding this "relevant task" from the description:

T277152: Display disambiguation information about a lexicon entry
Update Help:Extension:Wikispeech/Lexicon editor.

What exactly should be updated? Is it to explain the new display of for example?:

Id: 919477
Word: katt
Morphology: -
Part of speech: -
Paradigm: -

So my question is if I should wait for that task to be merged before I update the help image?

The help page should match the latest release so I don't think we should wait. Even if work has started on the other task we don't know how long it will take before it's done.

What exactly should be updated? Is it to explain the new display of for example?:

Have a look at where in the page it mentions that screen and expand it. At least under "Edit a word" it talks about what is shown.

There's one @since tag in includes/Segment/PartOfContent/Link.php that's "0.0.13" (probably my fault 🙈).

Change #1203378 merged by jenkins-bot:

[mediawiki/extensions/Wikispeech@master] Release version 0.1.13

https://gerrit.wikimedia.org/r/1203378

@Sebastian_Berlin-WMSE I have updated producer now, but I can't update the https://meta.wikimedia.org/wiki/User:Sebastian_Berlin_(WMSE)/js/wikispeech.js since I don't have permission for that:

You do not have permission to edit this page, for the following reason:
You do not have permission to edit this JavaScript page because it contains another user's personal settings.

Now both producer and demo-wiki are updated. I kept the Wikispeech.bak-backups on the servers if something seems not to be working, but from what I can see it seems to work.

I have also requested that the MediaWiki:Gadget-Wikispeech.js on SVWP should be changed:
MediaWiki:Gadget-Wikispeech.js request - 11 november

The tag points to wrong commit, so I will fix this

Viktoria_Hillerud_WMSE changed the point value for this task from 16 to 3.Nov 12 2025, 9:44 AM
This comment was removed by Viktoria_Hillerud_WMSE.

The tag points to wrong commit, so I will fix this

Now it should finally be fixed @Sebastian_Berlin-WMSE

Yes, looks good.

Feel free to add any clarifications to 2. in the next release task to avoid confusion in the future. Maybe a general thing at the top that the items should be done in sequence. I.e. 1. should be finished before starting on 2. etc.