|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> We have lost many person hours by assuming no harm would come from installing this update.
There is a notification on the plugin's Wiki page
> This is the first time in my use of jenkins that updating to the latest version has bitten me.
Heh, you are really lucky. BTW, you are right that such approach hardly affects users.
I'm responsible for this f*ckup, because I've released a version without long-run testing on development servers.
BTW, we have been waiting for @abayer's review of PR #6 and PR #10 for more than 1 month...
> There should be a mechanism to prevent a plugin with such an issue being presented to end users.
AFAIK in the open-source version of update center there is no such features.