On 21.05.2015, at 10:03, PoisoN PoisoN <[email protected]> wrote:
> Any chance to get this request resolved?
It would help if you could explain the technical reasons that require this to
be a new plugin, rather than e.g. a simple new plugin release. (And if we can
get these issues resolved for the benefit of your users, all the better!)
So far, it only looks like you want to erase the old plugin name and establish
the new one to match your renamed product:
> Old name ("Serena Deploy plugin") is not suitable as Serena has many products
> and the plugin integrates only with one of them.
It seems unnecessary to force users to configure things all over again when
they want to get a new plugin version just because the service they're using
has been renamed. Couldn't you just change the display name of the plugin? Note
that when the new plugin isn't offered as update to the installed plugin via
the update center, it may result in fewer users moving to your new release,
keeping the old name around much longer.
Creating a new Git repo, losing all history, also seems like an excessive cut
with the past of the plugin. The new plugin is clearly based on the old one.
> Also to avoid upgrade issues it should be separate plugin with new plugin id.
It is unclear what kind of issues these are. Did you refactor the plugin so the
old configuration is incompatible and cannot be upgraded? If so, this should be
reworked if possible:
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Compatibilitymatters
If that's not possible, or if you don't want users to accidentally upgrade
before certain preconditions are met, you can declare the new release
incompatible with older ones, suggesting that users read the plugin changelog
before upgrading:
https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions
If there are technical changes to the service that prevent the older version
from working beyond a certain date, a minor update to the original release
could add a note to Jenkins warning users of that change, followed by a '2.0'
release that works with the reworked service.
Or maybe there is a reason for a user to run both plugins in parallel, because
they use two different versions of your service in parallel?
--
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/9E8734BB-F6F1-45B1-AC51-B6BFE5466C21%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
