On Friday, March 29, 2013 at 2:32 AM, Tyler Romeo wrote:
Quick question. If I'm correct, Vagrant is supposed to be for setting up
development environments. Under this assumption, why is the mediawiki git
repository only fetched with a depth of 1? Isn't is pretty useless to have
a development
On Sun, Mar 31, 2013 at 3:12 AM, Ori Livneh o...@wikimedia.org wrote:
You can use a shallow clone to pull new changes. As far as committing,
'git review -s' will actually trigger fetching the entire history. So this
way the bandwidth costs of pulling the entire history are deferred until
you
On 30.03.2013, 2:40 Asher wrote:
Why don't we continue to use the bits cache for all things
resourceloader. Can you provide a different path for these requests, such as
instead of:
http://bits.wikimedia.org/en.wikipedia.org/load.php?..
use something like:
I would like to announce the release of MediaWiki language extension
bundle 2013.03
This release is compatible with MediaWiki 1.20.3.
*
https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar.bz2
* sha256sum: be4c6b5f80e27396555dc09cef0cec92c78cca9eeef796a230da281734738810
I put together the 1.21.0rc1 this afternoon. I'll announce it shortly,
but, first, some observations.
* When you add or remove a configuration variable, it should have
release notes. When you update the release notes, please make sure that
you also update MW.o. A number of variables are
Are we going to do something about the ~200 (?) estimated bug fixes
without a release note, and other missing release notes?
https://www.mediawiki.org/wiki/Thread:Manual_talk:Coding_conventions/Release_notes_and_bug_fixes
Nemo
___
Wikitech-l mailing
I've just finished preparing the first release candidate for MediaWiki
1.21 and I'd like your help testing it before the final release.
Please download the release candidate and test it. If you find any bugs
please report them on Bugzilla[1] and make sure I am added as a CC so
that we can fix
MediaWiki Bugzilla Report for March 25, 2013 - April 01, 2013
Status changes this week
Reports changed/set to UNCONFIRMED: 33
Reports changed/set to NEW: 586
Reports changed/set to ASSIGNED : 75
