Hi,
On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
> changed:
>
> https://bluejeans.com/396234560
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
-Jeremy
Hello,
can someone to update list https://phabricator.wikimedia.org/P10500 which
contains repositories which haven't mediawiki/mediawiki-codesniffer.
I found in list that much repositories are empty, and repositories which
aren't available on Gerrit.
So, can someone please update this list of repositories (in
mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at
least, contains one PHP file. or to provide me command with which I can
update list when I want, so I don't need to request it every time.
Best regards,
Zoran.
P. S.: Happy weekend! :)
Last week, I spoke to a few of my Wikimedia Foundation colleagues about how
we deploy code—I completely botched it.
At the end of the conversation, I was pretty sure I'd only succeeded in
making a complex process more opaque. I decided to write a blog to redeem
myself: How We Deploy Code
<https://phabricator.wikimedia.org/phame/post/view/253/how_we_deploy_code/>
My goal was to write a very high-level overview of the process we use to
deploy code to Wikimedia production.
Hopefully, this is helpful.
<3
– Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
I'm confused about what the term "ltsrel" means. The way I understand it,
it *should* mean that the extension supports only Long Term Support
versions of MediaWiki. It would have a branch for every LTS version of
MediaWiki like REL1_31 and REL1_35, but not for REL1_32, REL1_33 or REL1_34.
However, on the Compatibility
<https://www.mediawiki.org/wiki/Compatibility#MediaWiki_extensions> page,
the rel and ltsrel policies are described as:
* release branches (key: rel): For every MediaWiki release, there is a
corresponding branch in the extension. So e.g. if you use MediaWiki 1.36,
you should use the REL1_36 branch of the extension.
* long-term support release branches (key: ltsrel): For every MediaWiki
release, there is a corresponding branch in the extension, following the
Version lifecycle release policy.
These sound exactly alike to me.
Hello everyone,
MediaWiki 1.31 has reached EOL. Consequently, Parsoid/JS (the javascript
version of Parsoid) is also EOL starting today.
Parsoid was originally implemented in Javascript. It was ported to PHP
in 2019 and the PHP port is now part of all MediaWiki releases. With the
EOL of the MediaWiki 1.31 LTS, LTS support transfers to Parsoid/PHP
0.12, which was included as part of the MediaWiki 1.35 LTS distribution.
Parsoid/JS has only been receiving security releases since 2020 and will
no longer get any security updates. We recommend all Parsoid users
switch over to Parsoid/PHP.
Subbu.
on behalf of the Content Transform Team (formerly the “Parsing Team”)
This release includes Node.js 12 and npm 7.
Get started by installing, updating, or learning more, at:
https://gerrit.wikimedia.org/g/fresh#fresh-environment
Changelog:
https://gerrit.wikimedia.org/g/fresh/+/21.09.1/CHANGELOG.md
This release upgrades the default "fresh-node" command to the latest WMF CI
image for Node.js, which bundles Node.js 12 and npm 7. It is based on
Debian 11 ("Bullseye") and includes Firefox 78 and Chromium 90 as well.
The previous Node.js 10 environment remains available as "fresh-node10" in
case you need it during the transition over the coming weeks. It will
likely be removed within a month or two. If you encounter problems with
Node.js 12, let us know on Phabricator! [1]
This release also introduces a "fresh-node14" command for experimention
with Node.js 14.
Fresh is a fast way to create isolated environments from your terminal.
These can be used to more securely work with 'npm' developer tools such as
ESLint, QUnit, Grunt, Selenium, and more. Example guide:
https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing
--
Timo Tijhof
[1] https://phabricator.wikimedia.org/tag/fresh/
As per the MediaWiki version lifecycle[1], I would like to announce the
formal end of life (EOL) of MediaWiki 1.31 as of tomorrow, Thursday
September 30, 2021, coinciding with the final security and maintenance
release for the branch, 1.31.16.
This means that MediaWiki 1.31 will no longer receive maintenance or
security backports. It is therefore strongly discouraged that you continue
to use it.
It is recommended to upgrade to MediaWiki 1.35, the current Long Term
Support (LTS) version which is not due to become EOL until September 2023.
MediaWiki 1.35 bumps the required PHP version from 7.0 in 1.31 (which is
unsupported upstream), to PHP 7.3.19 or later.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.31.16
- 1.35.4
- 1.36.2
This will resolve 3 issues in MediaWiki core and also includes some fixes
previously committed to git, including minor security and hardening patches
along with bug fixes included for maintenance reasons.
It also fixes 1 issue in a MediaWiki tarball bundled extension.
We will make the fixes available in these respective release branches,
master and the currently unreleased 1.37 branch. Tarballs will be available
for the above mentioned point releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow.
As a reminder, 1.31 (the old LTS) was due to become end of life (EOL) in
June 2021. 1.35 (the new LTS) is supported until September 2023. However,
to try and meet our LTS-LTS overlap commitments (1.35 was late due to
COVID), 1.31 got best-efforts extra support until the end of September 2021.
As the end of September 2021 is now upon us, this means 1.31.16 will be the
final security (and maintenance) release, and therefore it is considered
EOL as of tomorrow, September 30, 2021.
[1] https://www.mediawiki.org/wiki/Version_lifecycle