Change 942693 had a related patch set uploaded (by Jforrester; author: Jforrester):

[mediawiki/extensions/WikiLambda@master] Special:CreateObject: Restrict rights to 'wikilambda-create' not 'createpage' right

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

Change 942693 merged by jenkins-bot:

[mediawiki/extensions/WikiLambda@master] Special:CreateObject: Restrict rights to 'wikilambda-create' not 'createpage' right

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

Checked on wikifunctions beta:

Note: the links on wikidata refer to the documentation in Wikidata namespace, e.g. https://www.wikidata.org/wiki/Wikidata:Administrators. On wikifunctions beta, red links look as follows: https://wikifunctions.beta.wmflabs.org/w/index.php?title=Functioneers&action=edit&redlink=1

Still not deployed until the next train.

In T342859#9070557, @Jdforrester-WMF wrote:

Still not deployed until the next train.

Yes, so we keep tasks in To deploy column to indicate what tasks will go to production? Usually, Verify in production column means that all work (testing and dev work) is finished and the fix only needs to be checked in production.

In T342859#9070560, @Etonkovidova wrote:

In T342859#9070557, @Jdforrester-WMF wrote:

Still not deployed until the next train.

Yes, so we keep tasks in To deploy column to indicate what tasks will go to production? Usually, Verify in production column means that all work (testing and dev work) is finished and the fix only needs to be checked in production.

Yes, that was the plan – I was suggesting that "To deploy" means wait for the next deploy window (e.g. config) or train (regular patch), or backport (if needed); "Verify in Prod" means "this is now live and should be signed off or trigger re-work".

As said this week, these columns are likely to change, as we adjust to them.

In T342859#9070563, @Jdforrester-WMF wrote:

In T342859#9070560, @Etonkovidova wrote:

In T342859#9070557, @Jdforrester-WMF wrote:

Still not deployed until the next train.

Yes, so we keep tasks in To deploy column to indicate what tasks will go to production? Usually, Verify in production column means that all work (testing and dev work) is finished and the fix only needs to be checked in production.

Yes, that was the plan – I was suggesting that "To deploy" means wait for the next deploy window (e.g. config) or train (regular patch), or backport (if needed); "Verify in Prod" means "this is now live and should be signed off or trigger re-work".

As said this week, these columns are likely to change, as we adjust to them.

Thank you, @Jdforrester-WMF for clarification!