BTW

On Thu, Feb 8, 2018 at 5:16 PM, Jesse Glick <jgl...@cloudbees.com> wrote:
> why are you treating core and plugins as distinct things?

was meant as a fairly technical comment about the packaging design.
The goal here makes a lot of sense.


On this topic, is there any information on how you would propose new
snapshots of the system (core + plugin versions, I guess) get
“promoted” or “tagged” or whatever by Jenkins devs?

https://github.com/jenkinsci/jep/blob/master/jep/301/README.adoc#infrastructure-requirements

mentions that there would be some kind of build and test
infrastructure, but that is about it. A topic for another JEP?

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Fqg33g%2B7jOTY4Q6RsaGD%3DkfUKmsOcVuXtZzqNwLqkNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to