Thu, Feb 13
@daniel Testing of the scenarios above was successful except for the one test that was impossible. I created 4 new alternative tests for that one. Ready to resolve?
Is this task ready for code review by the Core Platform Team? The only patch I see is 475930, and it is marked as WIP. I'm untagging us for now, but please retag when there is a patch ready for code review.
Untagging task automatically tagged by Herald.
Wed, Feb 12
Wed, Feb 5
Mon, Jan 27
Thanks for the reminder. I will check on this.
Fri, Jan 24
Thu, Jan 23
The approach mentioned in T232140#5783295 (to replace the config variables wgLogo, wgLogoHD, wgMinervaCustomLogos and wgVectorPrintLogo with a single config variable wgLogos while maintaining backward compatibility to wgLogo) sounds reasonable. What will be the strategy for deprecating wgLogo?
Jan 17 2020
What is the status of this work? It is currently on the contractor workboard, but I'm not sure that is correct.
Resolved by T232634.
Resolved by T232634.
We will not be implementing this feature at this time.
Jan 16 2020
Yay! Thank you!
Remove CPT tag automatically added by Herald.
Removing CPT tag automatically added by Herald.
Removing tag automatically added by Herald.
@WDoranWMF Is there work for CPT here past changing the RESTBase configuration?
Is there a patch that you need review on? Please let us know what work you need from CPT. Untagging CPT for now.
It isn't clear to us what work there is for CPT on this task. We think the CPT tag was inherited from the parent task, so I'm untagging CPT. Feel free to retag with an explanation if there is work for us.
I don't believe there is anything for CPT to do here, but let us know if that is incorrect.
Jan 15 2020
Can the tests be run with a bot password?
Jan 14 2020
Jan 7 2020
Dec 20 2019
What is the severity of this? We are looking into it. In the future, please feel free to tag Core Platform Team for RESTBase issues.
Dec 19 2019
Thanks for your work on this @Jdforrester-WMF! If I understand correctly from @Osnard, they only support LTS releases so as a matter of course remove the non-LTS branches to prevent folks from relying on unsupported/untested branches. This does not align completely with either the master or release branch compatibility policies . The automatic release branch generation causes similar issues with the master compatibility policy. I'm not sure what an ideal resolution for this would be, but I'm noting this here for informational purposes since @Osnard is unavailable to comment right now.
Dec 18 2019
Dec 17 2019
You need to install the php-ldap package and restart apache.