@Daniel Beck You said typically, is there any way you can make an exception in this one instance? Most people don't care but in this instance I care simply because it's the initialy release. I don't plan on releasing unusable releases in the future either. I would simply do a 1.0.1 if i had kept the release tags in my github repository but i didn't. Now if i could do it myself i would but i can't and i have to ask for help.
FYI, a useful addition/warnings/notices to add to https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins would be How to setup the Jenkins Cloudbee's github webhooks and a notice about that default builds on jenkins.ci.cloudbees.com are configured with Java 7 because Jenkins itself is always supposed to be compatible with J7, the build can be configured to use J8 but in that case you'll have to correctly document that your plugin won't run on instances using J7. Sadly there is no metadata in the update center to let users know it from the plugins manager. I can add it myself if you like later on. -- 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/51c67632-e7a9-46f4-b111-5ef371fd667b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
