Jrbranaa (Jean-Rene Branaa)
Senior Quality Analyst

Projects (7)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Jan 9 2017, 10:54 PM (53 w, 2 d)
Availability
Available
IRC Nick
jrbranaa
LDAP User
Jrbranaa
MediaWiki User
Unknown

Recent Activity

Thu, Jan 11

Jrbranaa updated subscribers of T182635: Explain to TechComm (Daniel K) part of learnings from ORES post-mortem re arch reviews.

Sent off email to @daniel before the holidays with some observations and questions regarding the review queue process as it stands today and areas that we could improve it. I think the question is two-fold: What review should we do prior to deploying something into production for the first time vs what should we do on an ongoing basis when something is in production.

Thu, Jan 11, 8:09 PM · Release-Engineering-Team (Kanban)

Fri, Jan 5

Jrbranaa added a comment to T182749: Track test code coverage long term.

Would this by chance be an approach to storing other CI data longer terms as well (i.e., test results)?

Fri, Jan 5, 6:06 PM · MediaWiki-Core-Tests, MediaWiki-Platform-Team (MWPT-Q3-Jan-Mar-2018)

Thu, Jan 4

Jrbranaa added a comment to T1287: Define the architecture areas for MediaWiki core and platform extensions.

@Catrope, yes I think this is related.

Thu, Jan 4, 6:16 AM · Developer-Wishlist (2017), DevRel-October-2015, DevRel-September-2015, TechCom, Documentation, MediaWiki-Documentation, Developer-Relations

Tue, Dec 26

Jrbranaa added a comment to T182731: Investigate the Extension Submittal Review process.

Reached out to Daniel for more info. Also reached out to Marko regarding the review process for services.

Tue, Dec 26, 10:54 PM · Release-Engineering-Team (Kanban)

Dec 13 2017

Jrbranaa created T182733: Address proximity of service deployments to train deployments problem.
Dec 13 2017, 12:00 AM · Wikimedia-Incident, Release-Engineering-Team (Kanban)

Dec 12 2017

Jrbranaa created T182731: Investigate the Extension Submittal Review process.
Dec 12 2017, 11:54 PM · Release-Engineering-Team (Kanban)

Dec 11 2017

Jrbranaa moved T175181: [Technical Debt Series]What is Technical Debt from In-progress to Done (within RelEng) on the Release-Engineering-Team (Kanban) board.
Dec 11 2017, 5:20 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa moved T175183: [Technical Debt Series]How to remove Technical Debt from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Dec 11 2017, 5:20 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa moved T175184: [Technical Debt Series]Avoiding New Technical Debt from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Dec 11 2017, 5:20 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa closed T174093: FY2017/18 Program 3 Outcome 2 Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt, a subtask of T174089: FY2017/18 Program 3 Outcome 2: Organizational technical debt is reduced., as Resolved.
Dec 11 2017, 5:18 PM · Release-Engineering-Team, Epic
Jrbranaa closed T174093: FY2017/18 Program 3 Outcome 2 Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt as Resolved.
Dec 11 2017, 5:18 PM · RelEng-Archive-FY201718-Q2, Epic

Nov 24 2017

Jrbranaa added a comment to T173349: Identify Orphaned components/code.

Yeah, that's a good point. One of the thoughts that I've been having is to recognize "stewardship" outside of the foundation and sister orgs. Meaning, anyone can agree to be a steward provided they are willing and capable of being a steward as defined (whatever that ends up looking like).

Nov 24 2017, 8:27 PM · Release-Engineering-Team (Kanban)

Nov 14 2017

Jrbranaa added a comment to T170951: Please create new maillist named : code-health@lists.wikimedia.org..

Got it. Thanks!

Nov 14 2017, 9:50 PM · Wikimedia-Mailing-lists

Nov 13 2017

Jrbranaa moved T174093: FY2017/18 Program 3 Outcome 2 Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Nov 13 2017, 5:48 PM · RelEng-Archive-FY201718-Q2, Epic

Nov 10 2017

Jrbranaa added a comment to T174093: FY2017/18 Program 3 Outcome 2 Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt.

@greg Created a page with program management information. See: https://www.mediawiki.org/wiki/Technical_Debt_Program/Program_Management

Nov 10 2017, 10:35 PM · RelEng-Archive-FY201718-Q2, Epic
Jrbranaa moved T173349: Identify Orphaned components/code from Blocked (externally) to In-progress on the Release-Engineering-Team (Kanban) board.
Nov 10 2017, 6:57 PM · Release-Engineering-Team (Kanban)
Jrbranaa moved T173349: Identify Orphaned components/code from In-progress to Blocked (externally) on the Release-Engineering-Team (Kanban) board.
Nov 10 2017, 6:57 PM · Release-Engineering-Team (Kanban)
Jrbranaa triaged T175184: [Technical Debt Series]Avoiding New Technical Debt as Normal priority.
Nov 10 2017, 6:57 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa added a comment to T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations).

Changes to Developers/Maintainers page where reverted as they referred to an "in draft" page regarding stewardship, which I totally understand.

Nov 10 2017, 6:56 PM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa added a comment to T174091: FY2017/18 Program 3 Outcome 1 Objective 2: Identify and find stewards for high-priority/high use code segment orphans.

Updates have been made the the developers/maintainers page, but there are still gaps. Part of the challenge is that some are hesitant to claim "stewardship" without knowing what that will entail. Working on the definition in parallel.

Nov 10 2017, 6:48 PM · Release-Engineering-Team (Kanban), releng-201718-q3, RelEng FY201718 Q2 Goals, Epic
Jrbranaa added a comment to T175181: [Technical Debt Series]What is Technical Debt.

Final edits made (missed some later comments :-)). Requested final review to be done.

Nov 10 2017, 6:46 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa added a comment to T170951: Please create new maillist named : code-health@lists.wikimedia.org..

@Dzahn thanks for creating this. I didn't see an email come through with a password. Can you resend?

Nov 10 2017, 6:31 PM · Wikimedia-Mailing-lists

Nov 3 2017

Jrbranaa added a comment to T172845: What makes a high quality MediaWiki extension? - Hackathon session.

I like the concept of SourceRank and think something like that would be good for extensions. I think we'd want to add some additional code health attributes though. But I do like the inclusion of things like documentation. Perhaps another Rank attribute is whether or not the extension has a steward.

Nov 3 2017, 6:20 PM · MediaWiki-extensions-General, Wikimania-Hackathon-2017

Oct 31 2017

Jrbranaa added a comment to T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations).

Added first pass changes regarding code stewardship.

Oct 31 2017, 5:58 PM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic

Oct 24 2017

Jrbranaa added a subtask for T174091: FY2017/18 Program 3 Outcome 1 Objective 2: Identify and find stewards for high-priority/high use code segment orphans: T173349: Identify Orphaned components/code.
Oct 24 2017, 5:10 AM · Release-Engineering-Team (Kanban), releng-201718-q3, RelEng FY201718 Q2 Goals, Epic
Jrbranaa added a parent task for T173349: Identify Orphaned components/code: T174091: FY2017/18 Program 3 Outcome 1 Objective 2: Identify and find stewards for high-priority/high use code segment orphans.
Oct 24 2017, 5:10 AM · Release-Engineering-Team (Kanban)
Jrbranaa removed a subtask for T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations): T173349: Identify Orphaned components/code.
Oct 24 2017, 5:09 AM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa removed a parent task for T173349: Identify Orphaned components/code: T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations).
Oct 24 2017, 5:09 AM · Release-Engineering-Team (Kanban)
Jrbranaa added a subtask for T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations): T173349: Identify Orphaned components/code.
Oct 24 2017, 5:08 AM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa added a parent task for T173349: Identify Orphaned components/code: T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations).
Oct 24 2017, 5:08 AM · Release-Engineering-Team (Kanban)
Jrbranaa moved T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations) from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Oct 24 2017, 5:05 AM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa moved T174091: FY2017/18 Program 3 Outcome 1 Objective 2: Identify and find stewards for high-priority/high use code segment orphans from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Oct 24 2017, 5:05 AM · Release-Engineering-Team (Kanban), releng-201718-q3, RelEng FY201718 Q2 Goals, Epic
Jrbranaa claimed T174095: FY2017/18 Program 3 Outcome 2 Objective 2: Define and implement a process to regularly address technical debt across the Foundation.
Oct 24 2017, 5:03 AM · Release-Engineering-Team (Next), Epic
Jrbranaa claimed T174093: FY2017/18 Program 3 Outcome 2 Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt.
Oct 24 2017, 5:03 AM · RelEng-Archive-FY201718-Q2, Epic
Jrbranaa claimed T174089: FY2017/18 Program 3 Outcome 2: Organizational technical debt is reduced..
Oct 24 2017, 5:02 AM · Release-Engineering-Team, Epic
Jrbranaa claimed T174091: FY2017/18 Program 3 Outcome 1 Objective 2: Identify and find stewards for high-priority/high use code segment orphans.
Oct 24 2017, 5:01 AM · Release-Engineering-Team (Kanban), releng-201718-q3, RelEng FY201718 Q2 Goals, Epic
Jrbranaa reopened T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations) as "Open".
Oct 24 2017, 5:01 AM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa reopened T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations), a subtask of T174088: FY2017/18 Program 3 Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced., as Open.
Oct 24 2017, 5:01 AM · Release-Engineering-Team, Epic
Jrbranaa closed T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations), a subtask of T174088: FY2017/18 Program 3 Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced., as Resolved.
Oct 24 2017, 5:01 AM · Release-Engineering-Team, Epic
Jrbranaa closed T174090: FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations) as Resolved.
Oct 24 2017, 5:01 AM · RelEng-Archive-FY201718-Q2, RelEng FY201718 Q2 Goals, Epic
Jrbranaa claimed T174088: FY2017/18 Program 3 Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced..
Oct 24 2017, 5:01 AM · Release-Engineering-Team, Epic
Jrbranaa claimed T174087: FY2017/18 Program 3: Addressing technical debt.
Oct 24 2017, 5:00 AM · Release-Engineering-Team, Epic
Jrbranaa claimed T174096: FY2017/18 Program 3 Outcome 2 Objective 3: Promote and surface important technical debt topics at large gatherings of Wikimedia developers (e.g., DevSummit and Hackathon(s)).
Oct 24 2017, 5:00 AM · Release-Engineering-Team (Kanban), Epic

Oct 23 2017

Jrbranaa added a comment to T173349: Identify Orphaned components/code.

@Aklapper at this point the scope is what's listed at https://www.mediawiki.org/wiki/Developers/Maintainers. However this is the time to expand (or contract) as necessary.

Oct 23 2017, 4:49 PM · Release-Engineering-Team (Kanban)
Jrbranaa added a comment to T175181: [Technical Debt Series]What is Technical Debt.

Due to have it up for review 20171023.

Oct 23 2017, 4:45 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content

Oct 5 2017

Jrbranaa reopened T175181: [Technical Debt Series]What is Technical Debt as "Open".
Oct 5 2017, 6:30 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa closed T175181: [Technical Debt Series]What is Technical Debt as Resolved.
Oct 5 2017, 6:30 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa added a comment to T173349: Identify Orphaned components/code.

Have received a fair bit of feedback/recommendations on some of the orphaned components. Will be updating the Developers/Maintainers page with those that are straight forward, and seeking additional clarification on those that aren't.

Oct 5 2017, 6:29 PM · Release-Engineering-Team (Kanban)
Jrbranaa closed T175187: Code Health and the Code Health Group as Resolved.

Sorry Mel, should have looked at this task prior to asking you about the status.

Oct 5 2017, 6:28 PM · RelEng-Archive-FY201718-Q2, Wikimedia-Blog-Content

Sep 26 2017

Jrbranaa closed T173351: Setup Tech Debt SIG meetings as Resolved.
Sep 26 2017, 9:19 PM · RelEng-Archive-FY201718-Q1, Technical-Debt
Jrbranaa added a comment to T173351: Setup Tech Debt SIG meetings.

Held both initially scheduled video-based SIG sessions. Notes available. Will look to setup an IRC based session too.

Sep 26 2017, 9:19 PM · RelEng-Archive-FY201718-Q1, Technical-Debt

Sep 12 2017

Jrbranaa updated the task description for T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending.
Sep 12 2017, 10:09 PM · RelEng-Archive-FY201718-Q1
Jrbranaa closed T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending as Resolved.

Per our chat. I'd like to get some more info from you if possible. We could do it async or in a quick meeting if you'd prefer.

Sep 12 2017, 10:08 PM · RelEng-Archive-FY201718-Q1
Jrbranaa closed T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending, a subtask of T173462: LinksUpdate::acquirePageLock: Cannot flush pre-lock snapshot because writes are pending, as Resolved.
Sep 12 2017, 10:08 PM · MW-1.30-release-notes (WMF-deploy-2017-08-15 (1.30.0-wmf.14)), Patch-For-Review, Performance-Team, MediaWiki-JobQueue, Wikimedia-log-errors

Sep 7 2017

Jrbranaa moved T175181: [Technical Debt Series]What is Technical Debt from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Sep 7 2017, 5:38 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa moved T175187: Code Health and the Code Health Group from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Sep 7 2017, 5:38 PM · RelEng-Archive-FY201718-Q2, Wikimedia-Blog-Content

Sep 6 2017

Jrbranaa triaged T175187: Code Health and the Code Health Group as Normal priority.
Sep 6 2017, 6:08 PM · RelEng-Archive-FY201718-Q2, Wikimedia-Blog-Content
Jrbranaa created T175187: Code Health and the Code Health Group.
Sep 6 2017, 5:38 PM · RelEng-Archive-FY201718-Q2, Wikimedia-Blog-Content
Jrbranaa created T175184: [Technical Debt Series]Avoiding New Technical Debt.
Sep 6 2017, 5:34 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa created T175183: [Technical Debt Series]How to remove Technical Debt.
Sep 6 2017, 5:29 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content
Jrbranaa created T175181: [Technical Debt Series]What is Technical Debt.
Sep 6 2017, 5:25 PM · Release-Engineering-Team (Kanban), Wikimedia-Blog-Content

Sep 1 2017

Jrbranaa triaged T173349: Identify Orphaned components/code as Normal priority.
Sep 1 2017, 3:44 AM · Release-Engineering-Team (Kanban)
Jrbranaa triaged T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending as Normal priority.
Sep 1 2017, 3:42 AM · RelEng-Archive-FY201718-Q1
Jrbranaa triaged T173351: Setup Tech Debt SIG meetings as Normal priority.
Sep 1 2017, 3:37 AM · RelEng-Archive-FY201718-Q1, Technical-Debt
Jrbranaa closed T173435: 20170721-Train-Wikidata - Post mortem as Resolved.
Sep 1 2017, 3:35 AM · RelEng-Archive-FY201718-Q1
Jrbranaa added a comment to T173435: 20170721-Train-Wikidata - Post mortem.

Postmortem meeting etherpad notes available at: https://etherpad.wikimedia.org/p/20170831-Post_Mortem-T164173.

Sep 1 2017, 3:34 AM · RelEng-Archive-FY201718-Q1

Aug 24 2017

Jrbranaa added a project to T172850: Replace and deprecate abandoned LESS variable greys from Wikimedia products: Technical-Debt.
Aug 24 2017, 6:44 PM · MW-1.30-release-notes (WMF-deploy-2017-09-05 (1.30.0-wmf.17)), Technical-Debt, UI-Standardization-Kanban, UI-Standardization
Jrbranaa added a comment to T172850: Replace and deprecate abandoned LESS variable greys from Wikimedia products.

Thanks @Volker_E, I've noticed other examples where parent tasks are the tasks actually describing the technical debt aspect of the change and the subtasks are just work elements towards that goal. I think the description that you've provided is a good example of technical-debt - Going from a distributed approach to setting those values to a central approach. Reduces potential errors and makes life better for developers :-)

Aug 24 2017, 6:43 PM · MW-1.30-release-notes (WMF-deploy-2017-09-05 (1.30.0-wmf.17)), Technical-Debt, UI-Standardization-Kanban, UI-Standardization
Jrbranaa added a comment to T172166: Create "all transforms" demo.

Thanks for explaining. As something that helps development, I think its a good candidate for overall code health. I do like your definition.

Aug 24 2017, 12:08 AM · Technical-Debt, wikimedia-page-library

Aug 23 2017

Jrbranaa added a comment to T172166: Create "all transforms" demo.

Hello, not clear why this is marked as Tech-Debt. I know I'm missing some context, but I am looking to better understand our current working definition of Technical-Debt. thx

Aug 23 2017, 11:53 PM · Technical-Debt, wikimedia-page-library
Jrbranaa added a comment to T173281: $hidden unused in SpecialNewpages.

Cool. Makes sense. Thanks for the clarification.

Aug 23 2017, 11:30 PM · Technical-Debt, MediaWiki-Special-pages
Jrbranaa removed a project from T172850: Replace and deprecate abandoned LESS variable greys from Wikimedia products: Technical-Debt.
Aug 23 2017, 11:26 PM · MW-1.30-release-notes (WMF-deploy-2017-09-05 (1.30.0-wmf.17)), Technical-Debt, UI-Standardization-Kanban, UI-Standardization
Jrbranaa added a comment to T173281: $hidden unused in SpecialNewpages.

In "Dead", do you mean no longer used, or broken. If the prior, than yes minor TD, probably should be removed. If the later, then it's just a bug.

Aug 23 2017, 11:25 PM · Technical-Debt, MediaWiki-Special-pages
Jrbranaa added a comment to T172850: Replace and deprecate abandoned LESS variable greys from Wikimedia products.

Not clear to me why this is Technical Debt. If I understand this task correctly, it's abandoning/deprecating colors used in the UI. From what I can tell from the code changes, there was no refactoring done, just a change in color.

Aug 23 2017, 11:19 PM · MW-1.30-release-notes (WMF-deploy-2017-09-05 (1.30.0-wmf.17)), Technical-Debt, UI-Standardization-Kanban, UI-Standardization
Jrbranaa added a comment to T173281: $hidden unused in SpecialNewpages.

Not clear why this is tech-debt.

Aug 23 2017, 11:11 PM · Technical-Debt, MediaWiki-Special-pages
Jrbranaa added a comment to T173899: autoload.ide.php needs to be updated or removed.

Is this task considered TD because it's essentially duplicate code (reading into the "mostly copy-paste" comment)?

Aug 23 2017, 10:52 PM · Technical-Debt, MediaWiki-Core-Tests
Jrbranaa removed a project from T173900: Hide InputBox when printed: Technical-Debt.
Aug 23 2017, 10:43 PM · CSS, MediaWiki-extensions-InputBox
Jrbranaa added a comment to T173900: Hide InputBox when printed.

Not clear why this is considered technical-debt. I understand the desire for the change as described, but I wouldn't generally consider it TD. For more information on our evolving TD definition, please see: https://www.mediawiki.org/wiki/Technical_debt

Aug 23 2017, 10:42 PM · CSS, MediaWiki-extensions-InputBox
Jrbranaa added a comment to T7176: Make access declarations private protected and public really mean it.

This appears to be more of a general development practice/pattern request. Probably could address this concern (and possibly already is) as part of coding standards. We can then decide if refactoring to meet those standards is warranted through various ares of the codebase.

Aug 23 2017, 10:22 PM · WorkType-NewFunctionality, Technical-Debt, MediaWiki-General-or-Unknown
Jrbranaa added a comment to T173433: Expand on the incident report for wikidata wmf.10 - wmf.14 train deployment.

@daniel: Just a heads up that I will be sending out a request to have post-mortem participants refer to the incident report for background/context in preparation for the meeting. My plan is to send out the reminder August 25th 1:00 UTC. If you could have your input added by then, that would be helpful.

Aug 23 2017, 5:28 PM · RelEng-Archive-FY201718-Q1, Wikidata, Wikimedia-Incident
Jrbranaa moved T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Aug 23 2017, 4:45 PM · RelEng-Archive-FY201718-Q1

Aug 17 2017

Jrbranaa added a comment to T171852: Tech talk: Selenium tests in Node.js.

@zeljkofilipin, I'd like to create various "series" of tech talks, for example there will be a "Code Health" series, and perhaps, a "QA Series". Should we have this one be the first in a "Automated Testing Series" or something of that nature?

Aug 17 2017, 9:17 PM · RelEng-Archive-FY201718-Q2, Developer-Relations (Oct-Dec 2017), Browser-Tests-Infrastructure, User-zeljkofilipin

Aug 16 2017

Jrbranaa added a subtask for T173462: LinksUpdate::acquirePageLock: Cannot flush pre-lock snapshot because writes are pending: T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending.
Aug 16 2017, 11:54 PM · MW-1.30-release-notes (WMF-deploy-2017-08-15 (1.30.0-wmf.14)), Patch-For-Review, Performance-Team, MediaWiki-JobQueue, Wikimedia-log-errors
Jrbranaa added a parent task for T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending: T173462: LinksUpdate::acquirePageLock: Cannot flush pre-lock snapshot because writes are pending.
Aug 16 2017, 11:54 PM · RelEng-Archive-FY201718-Q1
Jrbranaa created T173477: wmf.14 Blocker - Post Mortem - Cannot flush pre-lock snapshot because writes are pending.
Aug 16 2017, 11:52 PM · RelEng-Archive-FY201718-Q1
Jrbranaa moved T173435: 20170721-Train-Wikidata - Post mortem from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Aug 16 2017, 5:30 PM · RelEng-Archive-FY201718-Q1
Jrbranaa created T173435: 20170721-Train-Wikidata - Post mortem.
Aug 16 2017, 5:28 PM · RelEng-Archive-FY201718-Q1
Jrbranaa moved T173349: Identify Orphaned components/code from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Aug 16 2017, 4:55 PM · Release-Engineering-Team (Kanban)
Jrbranaa moved T173351: Setup Tech Debt SIG meetings from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Aug 16 2017, 4:55 PM · RelEng-Archive-FY201718-Q1, Technical-Debt

Aug 14 2017

Jrbranaa created T173351: Setup Tech Debt SIG meetings.
Aug 14 2017, 9:32 PM · RelEng-Archive-FY201718-Q1, Technical-Debt
Jrbranaa created T173349: Identify Orphaned components/code.
Aug 14 2017, 9:22 PM · Release-Engineering-Team (Kanban)

Aug 11 2017

Jrbranaa added a comment to T172845: What makes a high quality MediaWiki extension? - Hackathon session.

One item that was discussed during the Vienna Hack-a-thon was having some form of rating system that would be available for extensions. This rating would be perhaps based on some objective measures (derived from some the criteria mentioned in this session) as well as some subjective developer ratings. Looking to do something like this for Code Health generally speaking.

Aug 11 2017, 6:24 PM · MediaWiki-extensions-General, Wikimania-Hackathon-2017

Aug 9 2017

Jrbranaa added a comment to T172845: What makes a high quality MediaWiki extension? - Hackathon session.

This is an interesting topic. During the hack-a-thon I did a session on "building better software" and one of the topics discussed was along these lines. We had some 3rd party users/developers of MediaWiki that wanted to see if there was a way to "rate" extensions based on certain criteria like your describing. Very interested in the outcome of this session (not there in person unfortunately).

Aug 9 2017, 4:11 PM · MediaWiki-extensions-General, Wikimania-Hackathon-2017

Jul 31 2017

Jrbranaa added a comment to T171852: Tech talk: Selenium tests in Node.js.

@zeljkofilipin sounds good. @Rfarrand I don't suspect that you'll need much from me on this one :-) I've got another series of TTs that I'll chat with you about soon.

Jul 31 2017, 6:29 PM · RelEng-Archive-FY201718-Q2, Developer-Relations (Oct-Dec 2017), Browser-Tests-Infrastructure, User-zeljkofilipin

Jul 27 2017

Jrbranaa added a comment to T171852: Tech talk: Selenium tests in Node.js.

@zeljkofilipin Rachel is still setting them up for us, by I offered to get them going and coordinating some topics. When do you want to do it?

Jul 27 2017, 4:15 PM · RelEng-Archive-FY201718-Q2, Developer-Relations (Oct-Dec 2017), Browser-Tests-Infrastructure, User-zeljkofilipin

Jul 21 2017

Jrbranaa added a comment to T170951: Please create new maillist named : code-health@lists.wikimedia.org..

Technical Debt and Code Health are definitely related. However, Code Health is a superset of Technical Debt. It covers the broader topic of how software was written and it's influence on readability, maintainability, stability, and simplicity. It's about helping the developers be more productive while increasing "developer happiness" and overall software quality.

Jul 21 2017, 11:28 PM · Wikimedia-Mailing-lists
Jrbranaa added a comment to T170951: Please create new maillist named : code-health@lists.wikimedia.org..

I'm hesitant to have Code Health discussions in the qa@ list due to the potential limitation in subscriber-ship/interest. It's my belief that Code Health discussions are intended for(if not sourced from) developers, engineering managers, in addition to those in more traditional QA roles. If we want to avoid the creation of another list, I'd propose that we use a broader engineering list. That being said, I'd still like to start with a separate list if possible.

Jul 21 2017, 10:42 PM · Wikimedia-Mailing-lists

Jul 19 2017

Jrbranaa closed T169779: Improve the Jenkins output to the QA-Alerts mail list as Invalid.

After further investigation, it appears that this isn't an output issue from Jenkins. I was receiving mail list digests and the "scrubbed html" content attached to it doesn't get automatically rendered by the browser and instead just loads the HTML source. Testing the html file outside of the digest seems to work fine and the html is properly rendered.

Jul 19 2017, 9:08 PM · RelEng-Archive-FY201718-Q1, Continuous-Integration-Infrastructure

Jul 18 2017

Jrbranaa triaged T170963: Create code health mailing list as Normal priority.
Jul 18 2017, 6:18 PM · RelEng-Archive-FY201718-Q1, Wikimedia-Mailing-lists
Jrbranaa created T170963: Create code health mailing list .
Jul 18 2017, 6:17 PM · RelEng-Archive-FY201718-Q1, Wikimedia-Mailing-lists