+1 from me for closing it. Do people have important things there, or can it
be 'deleted'?
On 27 January 2016 at 22:01, Chad wrote:
> On Wed, Jan 27, 2016 at 2:00 PM James Forrester
> wrote:
>
> > On 27 January 2016 at 13:57, Ori Livneh
On 27 January 2016 at 14:18, Alex Monk wrote:
> +1 from me for closing it. Do people have important things there, or can it
> be 'deleted'?
>
We could just move all the content into testwiki and redirect the domain.
;-)
J.
--
James D. Forrester
Lead Product Manager,
On 01/28/2016 08:57 AM, Ori Livneh wrote:
> The setup of test2.wikipedia.org is no longer meaningfully different from
> test.wikipedia.org. Is there a good reason for keeping test2?
Especially when debugging and testing cross-wiki features, it is
extremely useful to have two test wikis to use.
There appears to be one periodic Jenkins job running against test2wiki, and
it just started failing today, so we should investigate why.[1] Release
Engineering will look into moving this job to testwiki, but please don't
shut down test2wiki just yet.
[1]
3 things come to mind. Not so long ago an invitation was sent to wiki
communities to use that specific server for VE single edit tab testing. I think
that should be taken into account. Since this feature has not yet landed in
production, people might still be using that link to evaluate and
On 27 January 2016 at 17:16, Legoktm wrote:
> Especially when debugging and testing cross-wiki features, it is
> extremely useful to have two test wikis to use. MassMessage,
> GlobalCssJs, GlobalUserPage, and now cross-wiki notifications were all
> initially deployed
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-01-27
= 2015-01-27 =
== Product ==
=== Reading ===
Android
* Hotfix for login issues, v2.1.138, in production.
* v2.1.139 beta published for changes in Wiktionary API and removal of "m."
requests.
* Android saved synchronized articles
As we approach another quarterly planning cycle, I'd like to bring my
proposal for how we can improve our quarterly planning and review process.
https://www.mediawiki.org/wiki/Wikimedia_Engineering/Goals_Proposal
Do people support implementing these changes for the Q4 planning cycle? If
you have
Good evening. For the past week, my bot has intermittently been seeing this
error when it tries to edit or upload:
API Error: Array
(
[code] => badtoken
[info] => Invalid token
[*] => See http://commons.wikimedia.org/w/api.php for API usage
)
It is unpredictable; it will occasionally
On 28 January 2016 at 02:15, Legoktm wrote:
> Hi,
>
> On 01/27/2016 12:46 PM, Matthew Flaschen wrote:
> > On 01/25/2016 03:16 PM, Rob Lanphier wrote:
> >> In the short-term, I believe a non-Wikimedia focused subgroup of ArchCom
> >> may make sense. The declining
Hi,
On 01/27/2016 12:46 PM, Matthew Flaschen wrote:
> On 01/25/2016 03:16 PM, Rob Lanphier wrote:
>> In the short-term, I believe a non-Wikimedia focused subgroup of ArchCom
>> may make sense. The declining MediaWiki use outside of Wikimedia has
>> been
>> a longstanding problem for us, but not
On Tue, Jan 26, 2016 at 11:58 PM, Mukunda Modell
wrote:
> I think it would be very useful to have a way to, in addition to
> cache-busting, also force the request to be served from the pre-production
> branch rather that the current production branch. This way changes on
> Feature flagging or using feature branches for certain things may be a way
> to go for certain things, we're keeping that in mind definitely, thanks for
> the reminder Greg.
Just be clear: feature branches aren't feature flags and take you back
to a place closer to a 'dev' branch :).
> I
I'm seeing this error in the php log file
[Wed Jan 27 13:53:04.030488 2016] [:error] [pid 29314] [client
10.45.13.185:55154] PHP Warning: filemtime(): stat failed for
/app/mediawiki/mw/composer.lock in
/app/mediawiki/mw/extensions/Bootstrap/src/ResourceLoaderBootstrapModule.php on
line 210,
The setup of test2.wikipedia.org is no longer meaningfully different from
test.wikipedia.org. Is there a good reason for keeping test2?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 27 January 2016 at 13:57, Ori Livneh wrote:
> The setup of test2.wikipedia.org is no longer meaningfully different from
> test.wikipedia.org. Is there a good reason for keeping test2?
>
I'd be happy for it to be closed.
J.
--
James D. Forrester
Lead Product Manager,
On Wed, Jan 27, 2016 at 2:00 PM James Forrester
wrote:
> On 27 January 2016 at 13:57, Ori Livneh wrote:
>
> > The setup of test2.wikipedia.org is no longer meaningfully different
> from
> > test.wikipedia.org. Is there a good reason for keeping
On Wed, Jan 27, 2016 at 8:46 PM, Magog The Ogre
wrote:
> Good evening. For the past week, my bot has intermittently been seeing this
> error when it tries to edit or upload:
>
> API Error: Array
> (
> [code] => badtoken
> [info] => Invalid token
> [*] => See
Feature flagging or using feature branches for certain things may be a way
to go for certain things, we're keeping that in mind definitely, thanks for
the reminder Greg.
I agree with you regarding releases Gergo. The good thing about the
*release*s was mainly the curated changelog of changes for
On Wed, Jan 27, 2016 at 2:17 AM, Ori Livneh wrote:
>
> Well, there is a way: you can edit /srv/mediawiki/wikiversions.php on
> mw1017 to change the mapping of wikis to branches, and set the
> X-Wikimedia-Debug header to ensure your request gets handled by mw1017.
> Making
20 matches
Mail list logo