On Fri, Jun 28, 2019 at 11:36 AM 'Gavin Mogan' via Jenkins Developers <[email protected]> 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`. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3WH%3Dcpi4iAR6h_bUWNg6JL4Hef7uTw%2Bo5pubG8q6gfkA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
