Fri, Nov 15
Thanks for your feedback, I see your concerns. To be honest, I am also not very happy with the REL1_31_dev-branch-approach. But unfortunately I do not see any other way to do it. This is because of the fact that we are developing various versions in parallel. E.g. REL1_31 will be version "3.1.x" (next patch level release), while REL1_31_dev will already be a new minor version "3.2" (next minor-level-release), which may have new features. If we developed "3.2" functionality in REL1_31 and only release by tagging, we could not have patch-level releases once a single minor-level-feature was merged in one of the BlueSpice* repos.
Mon, Nov 11
@hashar I have uploaded a patchset for the cloner.py: https://gerrit.wikimedia.org/r/#/c/integration/quibble/+/550087/
ATTENTION: I am new to Python and did not test this code very well. Could you please have a look and give me some advice? Thanks in advance!
Fri, Nov 1
Thu, Oct 31
Wed, Oct 30
Tue, Oct 29
Mon, Oct 28
Okay. In that case it's actually not really required to fix this. But hey, now it's done 😀
Sun, Oct 27
Fri, Oct 25
Is this code only executed after checking for webauthn-capabilities?
Okay, thanks. So avoiding ES6 features as listed in your reference would be sufficient?
There is another issue... https://integration.wikimedia.org/ci/job/quibble-composer-mysql-php72-docker/6248/console
@Reedy Can you please clarify what exactly needs to be done? The statement "still written in ES6(!) so won't work in MW" is confusing me. The code was developed against the MediaWiki codebase that has been deployed to Wikipedia at the time when this extension was written. So why would it not work anymore?
Thu, Oct 24
Unfortunately this has not been resolved yet. As a workaround you can modiy https://github.com/wikimedia/mediawiki-extensions-LDAPProvider/blob/6ce932dd2a91d974bbd2d8cf71bfa53d6eca1a58/src/UserDomainStore.php#L27-L28 and just add
Wed, Oct 23
This one is still around: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/BlueSpiceConfigManager/+/542402/
Tue, Oct 22
Oct 18 2019
As far as I understand from @hashar's explanation in another place (T224285#5216226) this is because in mediawiki/core (and other extensions listed in the dependencies) there is no REL1_31_dev branch, therefore quibble falls back to master branch . But in master branch there are already libraries/dependencies used that do not support older PHP versions anymore.
Thank you very much.
Oct 17 2019
Updated docs on [[Extension:LDAPProvider]]
Oct 15 2019
@Paladox @hashar Sorry to bother you, but this is urgent to me. I need a bluespice-admin group with members Mglaser, Pwirth and Robert Vogel. Additionally I need all BlueSpice*-repos to allow Push to this group. What do I need to do? Can you please help me?
Oct 14 2019
Oct 9 2019
So no easy way to create a bluespice-admin group and set Push permission for all BlueSpice* repos?
Oct 8 2019
Oct 7 2019
Should be fixed in 3.1
Oct 1 2019
Yes, I actually want to push instead of review, as I just want to synchronize branches REL1_31 and REL1_31_dev. In REL1_31_dev everything has already been reviewed, so I don't want to review all those commits again when merging them into REL1_31. I believe the above workflow works just fine. The only issue is the Push permission. But there is a solution now.
Okay, I just set the Push permission to group bluespice on https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/BlueSpiceSignHere,access and now it works. Thank you very much.
I detail it says
Sep 30 2019
Sep 23 2019
@matmarex I am pretty sure that it works, as we use REL1_31 of VisualEditor in our current BlueSpice 3.1 Release. But I have to admit, that I didn't test it in a plain "MediaWiki-Core + VisualEditor" setup. Just as part of the whole BlueSpice distribution. We have already "backported" this to our "BlueSpiceVisualEditorConnector" extension . BlueSpice is always build with REL1_31 of MW Core and all extensions. I will ask one of my coworkers (@Intracomof, how about you?) to test it in a plain "MediaWiki-Core + VisualEditor" setup, though.