There have been several proposals for removal without deprecation in the past
few days, each with more impact on existing code - from "virtually certain
nobody ever used" to "the fix is trivial".
I know it is annoying as heck to keep outdated code, but if you ask me, unless
there is an
> So we have to make a trade-off between the burden on extension
> developers and on core developers. When it seems likely that
> basically no non-public extension/skin uses the feature, I think it's
> reasonable to say that we should do what's easiest for core
> developers. If a few people out
> of work they have to do. The deprecation policy is just to give
> extension maintainers a bit of breathing room so they don't have to
> scramble to update their extension before it breaks.
Exactly. It also makes it easier for them to maintain their extensions for more
than the last version of
Hallo Alexander,
könntest du bitte aufhören, mich als Vertreter der ESA zu führen. Ich bin
privat da und habe weder Genemigung noch Auftrag der ESA aufzutreten. Mit
Quality hab ich schon länger nix mehr zu tun. Schlimmstenfalls kriegt das
jemand in den falschen Hals und ich darf mich hier
‐‐‐ Original Message ‐‐‐
On Thursday, March 14, 2019 3:56 PM, David Barratt
wrote:
> Is the Wikimedia Foundation responsible for people's emotions?
Yes. Frustration, mostly. It is not entirely unexpected that this message
originates from @wikimedia.org.
So here is one vote in favor, if that helps.
Because seeing what is achieved and that there is somebody who actually cares
makes me a bit happier each week.
I do not find these threads too intrusive and there is too little positive
news, anyway.
Maybe, to help people filter these mails out
When running `composer update` MediaWiki injects a mediawiki/mediawiki package,
so extensions can declare a dependency on a particular MW version range.
However, when doing a `composer update --dry-run` this package gets not
injected causing the dry run to fail.
Does anybody know a
ction."
‐‐‐ Original Message ‐‐‐
On Friday, November 15, 2019 4:15 PM, David Barratt
wrote:
> as far as I know, extensions shouldn't be declaring a dependency on MediaWiki
> in composer.json and if one is, it should probably be fixed.
>
> On Fri, Nov 15, 2019 at 9:50
e declaring a dependency on
>> MediaWiki in composer.json and if one is, it should probably be fixed.
>>
>> On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l <
>> wikitech-l@lists.wikimedia.org> wrote:
>>
>>>
>>> When running `composer update`
The SimpleBatchUpload [1] extension uses the MW API to batch-upload files. In
the simplest case the user just goes to Special:BatchUpload, dumps a bunch of
files and they are uploaded in parallel.
I got a bug report recently [2] where I am not sure what to do:
"Our group has been using
10 matches
Mail list logo
