On Fri, Jun 28, 2019 at 11:36 AM 'Gavin Mogan' via Jenkins Developers
<
jenkin...@googlegroups.com> wrote:
> I'll do a formal review of the last one when the first two are finalized and released.
When a new API is being proposed, it is necessary to review the
proposed usages in tandem with the API itself. Otherwise you are not
verifying that the API solves a tangible problem in the most
straightforward manner. JEP-305 additionally helps you run CI against
downstream PRs, which is why #26 should first be merged and then #25
synchronized with `master`.