Specific to AMD OpenCL hardware or driver

the bug is not a bug, but a feature

someone needs to start working on that

he bug needs a fix outside of the scope of darktable, in an external lib or in a driver

someone is currently working on that, check with them before taking over

the bug needs a fix outside of the scope of darktable, at a theoretical level

pull request fixing a bug

this raises concerns, don't move on the technical work before reaching a consensus

default-behavior-change

Pull requests that update a dependency file

depends: external lib

depends: libraw

for libraw related issues

depends: rawspeed

cannot merge before rawspeed updated

depends: wayland

for wayland releated issues

difficulty: average

some changes across different parts of the code base

difficulty: good first contribution

easy enough for first-time contributors willing to dip their toes into darktable

difficulty: hard

big changes across different parts of the code base

difficulty: trivial

some changes in a couple of functions

documentation-complete

needed documentation is merged in dtdocs

documentation-pending

a documentation work is required

feature: enhancement

current features to improve

feature: exists

Requested functionality is already available, possibly via plugin

new features to add

feature: redesign

current features to rewrite

Fixed in master

Has already been fixed in current master branch

pull request needing changes to be merged

no-issue-activity

Related to darktable OpenCL code

core features are broken and not usable at all, software crashes

core features work as expected, only secondary/optional features don't

priority: medium

core features are degraded in a way that is still mostly usable, software stutters

Read the manual

release notes: pending

reproduce: confirmed

a way to make the bug re-appear 99% of times has been found

reproduce: peculiar

the bug seems to affect only a specific target and cannot be reproduced elsewhere

reproduce: random

the bug appears more than 30% of times but the causes are still unclear

scope: camera support

adding WB and raw support for new cameras

running darktable in command-line

scope: codebase

making darktable source code easier to manage

scope: color management

ensuring consistency of colour adaptation through display/output profiles

managing files, collections, archiving, metadata, etc.

scope: debugging

scope: hardware support

dealing with drivers and external devices: GPU, printers

scope: image processing

correcting pixels

scope: macos support

macos related issues and PR

scope: noise profile

adding noise profiles for new cameras

scope: OS support

making darktable work on particular operating systems

scope: performance

doing everything the same but faster

scope: software support

wiring external libs and software: LittleCMS, colord, G'MIC, enfuse/enblend, etc.

scope: translation / strings

make darktable international

user interface and interactions

scope: usermanual

improving the documentation

scope: windows support

windows related issues and PR

understood: clear

devs have a complete bug report with all the relevant info to start fixing

understood: incomplete

devs lack some important info to start fixing

understood: unclear

devs lack most or all important info and can do nothing, the report will be closed after 2 weeks

pull request in making, tests and feedback needed

No labels found. Sorry about that.