Using JEP process for future design changes to Declarative Pipeline?

[Liam Newman]

Andrew Bayer has been doing great work on Declarative pipeline.  He's done excellent work creating clear and understandable design discussions in JIRA and in the Pull Requests to the plugin. From design to implementation (including keeping documention) up to date, I think his work has been top notch. 

That said, JIRA and PRs are not the idea place to have design discussions nor the best place to document the reasoning behind those design choice.  Details get lost in long threads, it is not always clear what stage the design is at, and the actual final proposed design is sometimes less clear that it could be.  

Now that we have the Jenkins Enhancement Proposal process, I think it would be great if we started using it to track future design changes to Declarative Pipeline DSL.  

I'd like to know what folks (including Andrew) think of this idea? 

Thanks,

Liam Newman

Jenkins Evangelist

[Andrew Bayer]

fwiw, I am 100% behind the idea of JEP for non-trivial changes to Declarative.

A.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d48c4626-d7cc-4fa3-b281-caccd6e0f0cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Baptiste Mathus]

Sure, why not? I don't think JEP are designed to be limited to core.

But yes definitely we need to encourage more plugin developers to go through this process for the benefit of everyone wrt to (hopefully) engagement and more fluidity once validated by more eyes.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY2ozmpiw29hZVH%3DdpEmN8LJRYAKYb-3bn%3DBwQ_37qoDw%40mail.gmail.com.