Klemens Böswirth

Another important thing is that `default:/` keys should be processed in the `poststorage` phase of `kdbGet`, currently the are temporarily cut out during that phase.

> writing the change-tracking journal before the kdbSet commit happens Based on what I can see in #4892, I'd also say this would be very complicated to do. If we...

> I don't think "distributed transaction" would be necessary, we can simply fail if two kdbSet are executed at the same time? Not sure, sounds like without the lock there...

Not directly related to releases, but fits the general CI discussion here: Is there a way to tell Jenkins to prioritize the stages up to "Main Build" over the "Full...

Small update: 1. I will still write a migration script for `strerror`, but it will be specific to Elektra and rely on a `elektraStrError` function I'll add to `libelektra-core` or...

Correction to point 4 in the comment above: - `strtok` cannot be migrated with a generic script. A restricted script that makes some assumptions about how `strtok` is used (*1)...

The first question, before we can make any plans is: @mpranj do you have the time to work on this right now? If not, there is no point in trying...

The changes from `store_name.md` are not much, no. But depending on the outcome of #4641 and all the other decisions spawned from change tracking, there could be bunch more changes...

I disagree with the order. IMO it is clear COW needs to be worked on first. Everything else could use COW, depending on what COW looks like. Sure we could...

> Another task important to get the decisions done is to write use cases for Elektra's APIs. I don't know anyone more eminently suitable than @kodebach. I added the task...