Sorry, my bad. This is not what I want to say. I just want to note that it was very hard to find the solution for my problem(s). When I do a recap, it was probably better to read all the documentation top down.
Don't get me wrong, I joined the community some years ago, because I think jenkins was/is great and I want to do what I could do to make it a little bit greater. But as always in software projects the documentation sometimes not covers the things in a structure that all kinds of problems are in place for all types of persons. To make long story short, in my case I have troubles with releasing plugins. IMHO What about using our own infrastructure at https://jenkins.ci.cloudbees.com or https://ci.jenkins-ci.org to release the plugins? Thomas Am 26.11.2016 um 21:00 schrieb Daniel Beck: > >> On 26.11.2016, at 20:54, Baptiste Mathus <[email protected]> wrote: >> >> This is a wiki. Please feel free to fix outdated things. Or please, please, >> tell us what is outdated. I'm curious which one is. >> I think many pages should just be wiped out, or heavily shortened to keep >> the really important things, but doing that takes time. If things are >> outdated then it's just to be deleted, and we save time if you show us >> obviously outdated things... > This. > > We also have a new mailing list for collaborating on documentation now: > > https://groups.google.com/forum/#!forum/jenkinsci-docs > -- 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/bea5dfd5-7d7a-0f9d-ee27-1508a9fde7bb%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
