In the same vein as my previous email, I've written up a design document which outlines the current approach for packaging I intend to use for Jenkins Essentials:
https://github.com/jenkinsci/jep/tree/master/jep/301
I think it should be fairly straight-forward and understandable why I'm taking
the approach described, but if there any ambiguity do let me know.
Please take a look at the document and let me know what you think on this
thread :)
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: [email protected]
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
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/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
