On 13.12.2015, at 22:47, Marc Carter <drekb...@gmail.com> wrote: > 1.0-SNAPSHOT is mistake caused by myself
Snapshots don't matter. > 1.0.0, 1.0.1 and 1.0.2 were uploaded by someone random a month ago and are > not official (nor newer than 1.0). I'm sure they were just eager to see it > uploaded but let's clear house please. Could you confirm that the user 'arpitgold' has never been a contributor to or maintainer of ez-templates, and no reason to publish this plugin into our repo? FWIW we've always blacklisted versions from the update site in the past -- not sure whether it was easier than removing artifacts or for a different reason, so I'd like to keep to the established process for now. Alternatively, if you could release a 1.1, that would probably be best. > What is the policy on plugin dependencies? Clearly ez-templates has no > hard-req on anything newer than 1.574 but I don't just want to force users > onto the latest LTS (and would that be the initial LTS or the newest > maintenance release on that base...). What is recommended? No fixed rules. Keeping to an older core dependency is fine. A while back I added a section to this wiki page explaining the trade-off: https://wiki.jenkins-ci.org/display/JENKINS/Choosing+Jenkins+version+to+build+against Note that we *really* do prefer use of Jira for various reasons even if a small number of plugin developers disagrees -- while I doubt we'll ever shut down established GH trackers, we're disabling GH issues when forking for a reason. -- 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/D4B651D9-A0E0-4C6D-9124-78EF9FD6382F%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
