Unifying exceptions is critical for a sane protocol interconnect

Hi, does this new feature have planned target release, i.e. is this targeted for Chlorine/Argon?

First of all, this is an Epic covering two protocols as well as two distinct feature sets. That pretty much guarantees this will be delivered across a number of releases.
The issues in this epic are a very basic decomposition of what needs to happen to cover the basics of the specification. The list is likely to grow as the design/implementation proceeds, when it does.

There is at least one dependecy for the entire effort on which the design work, much less an actual implementation, has not started yet. There are a number of dependencies in the individual issues that need to be addressed before those issues can reasonably be worked on.

Given the number and the skillset of current full-time contributors (and delivering this item is a full-time effort), I cannot really estimate delivery times for the bits and pieces, much less for the entire epic.

The usual open-source mantra applies: "focus follows interest". It could be as soon as in 3 months, it could well be in 2 years.