Page MenuHomePhabricator

merl tools (tracking)
Closed, InvalidPublicFeature

Description

All issues that needs to be solved to run or enhance tools by merl


Version: unspecified
Severity: enhancement

Details

Reference
bz67556

Related Objects

StatusSubtypeAssignedTask
OpenFeatureNone
DeclinedNone
InvalidFeatureNone
Resolvedcoren
Resolvedcoren
Resolvedcoren
ResolvedNone
ResolvedRicordisamoa
DeclinedNone
Invalid Springle
Resolved Springle
Resolvedcoren
Declinedcoren
Resolvedcoren
Resolvedcoren
Resolvedcoren
ResolvedKrenair
ResolvedKrenair
ResolvedKrenair
Resolvedjcrespo
Resolveddcaro
DeclinedNone
Resolvedbd808
Resolvedbd808
Resolvedbd808
InvalidNone
ResolvedMarostegui
Resolvedbd808

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 3:36 AM
bzimport set Reference to bz67556.

Is this about changes in merl tools itself (because that's what this ticket is filed under, though merl tools does not have a Bugzilla component), or about Tools infrastructure on Labs? Or both mixed?

It is a tracking bug for features missing at labs, mediawiki, wikidata or any other component covered by this bugzilla that any of my tools relies on.

For my tools itself i am tracking bugs, new feature requests or future ideas at a private roundup installation and not at this bugzilla.

I had a long bug list of missing labs features i was watching the last year until i could start migrating. And i still have a long list of missing mediawiki features new bot features rely on. Maintaining and watching such a list stored locally is very uncomfortable. That's why i though creating a tracking bug would be a good idea.

I'll not start adding this as blocker to every old existing bug currently on my local list but for future bugs.

I hope this is ok.

In T69556#733019, @Merl wrote:

It is a tracking bug for features missing at labs, mediawiki, wikidata or any other component covered by this bugzilla that any of my tools relies on.

For my tools itself i am tracking bugs, new feature requests or future ideas at a private roundup installation and not at this bugzilla.

I had a long bug list of missing labs features i was watching the last year until i could start migrating. And i still have a long list of missing mediawiki features new bot features rely on. Maintaining and watching such a list stored locally is very uncomfortable. That's why i though creating a tracking bug would be a good idea.

I'll not start adding this as blocker to every old existing bug currently on my local list but for future bugs.

I hope this is ok.

And how can't you just request a component tag that like #tool-labs-tools-erwin's-tools or #tool-labs-tools-quentinv57's-tools ?

@Merl was last active in 2016. Hence I am resetting the assignee of this task.
Resetting the assignee avoids the impression that somebody is already working on this task.

It is unclear to me if someone else could potentially work on fixing this task, as I do not if the codebase is public and where it is located.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:14 AM