Hello,
We suffered an unexpected issue with the phabricator database replica,
which I believe it is used to generate these stats.
We will hopefully have it back up today and we can re-run the script.
Sorry for the inconveniences,
Manuel.
On Wed, Aug 1, 2018 at 3:01 AM, יגאל חיטרון wrote:
>
On 27/07/18 14:55, Tim Starling wrote:
> In the TechCom committee meeting yesterday, it was decided that next
> week's RFC meeting will discuss T198256 "Modern Event Platform -
> Choose Schema Tech"
>
> https://phabricator.wikimedia.org/T198256
>
> This relates to the choice between Avro and
Hi. All the data seems to be irrelevant - either empty or maximum.
Igal (User:IKhitron)
On Aug 1, 2018 03:00, wrote:
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2018-07):
Active Maniphest users (any activity) in (2018-07):
Task
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2018-07):
Active Maniphest users (any activity) in (2018-07):
Task authors in (2018-07):
Users who have closed tasks in (2018-07):
Projects which had at least one task moved from one
I favor deprecating functions. I'm sure you're familiar with
https://xkcd.com/1172/
Have a great day,
Bart Humphries
bart.humphr...@gmail.com
(909)529-BART(2278) <9095292278>
On Tue, Jul 31, 2018 at 3:16 PM, Alex Winkler
wrote:
> So to give my perspective as an "outsider":
>
> My day to day
So to give my perspective as an "outsider":
My day to day job is to write MediaWiki extensions for a wiki-farm
called Liquipedia. We are mostly hopping LTS version, so even
deprecation for two versions doesn't necessarily mean much to us here.
Generally I just install a new MediaWiki version
On Tue, Jul 31, 2018 at 3:46 PM, Stephan Gambke wrote:
> I agree that there is a trade-off to be done.
> I disagree about expecting code to be put where it is visible to core
> developers. I do appreciate that you go and look for where the
> functionality that you are working on is used outside
> 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
*Hello all,starting this week the Technical Advice IRC Meeting will take
place not only every Wednesday at 3 pm UTC, but also every first Wednesday
of the month at 11 pm UTC. This will allow people from other timezones to
attend.The Technical Advice IRC Meeting (TAIM) is a weekly support event
for
On Tue, Jul 31, 2018 at 10:43 AM, Stephan Gambke wrote:
> There are three "probability qualifiers" in that sentence (seems, probable,
> basically). You just don't know if somebody now has to fix their code.
Correct -- I can't know, because they didn't put their code in a place
where code search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I don't have a strong opinion about the specific function in this
case, but I did want to discuss a few things about the policy itself.
On 07/30/2018 06:28 AM, Stephan Gambke via Wikitech-l wrote:
> I know it is annoying as heck to keep
> 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
On Tue, Jul 31, 2018, 3:42 AM Derk-Jan Hartman
wrote:
> That is an impressive difference !
>
> On Mon, Jul 30, 2018 at 6:22 PM Amir Sarabadani <
> amir.sarabad...@wikimedia.de> wrote:
>
> > And this is the load on vslow database nodes on s7:
> >
> >
>
13 matches
Mail list logo
