This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/26058 [Failing Test]: Jav
Hi,
removing @Experimental and adding explicit @Stable annotation makes
sense to me. FWIW, when we were designing Euphoria API, we adopted the
following convention:
- the default stability of "evolving", @Experimental for really
experimental code [1]
- target @Audience of API [2] (pipeli
*;tldr - I'd like "evolving" to be further defined, specifically around how
we will make decisions about breaking behavior and API changes*
I don't particularly care what tags we use as long as they're well
documented. With that said, I think the following framing needs to be
documented with more
Honestly, I think APIs could be pretty simply defined if you think of it in
terms of the user:
@Deprecated = this was either stable or evolve but the
functionality/interface will go away at a future date
@Stable = the user of this API opting out of changes to functionality and
interface. For exam
Hi Juan Manuel montoya,
Thanks for working on this! Just for reference - all Beam Java artifacts are
normally built with Java 8 but they are tested and suposed to work with Java 11
and Java 17.
Also, it would be great to track a progress on this work for Debezium
integration by creating a Git
