|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
well 1.509 is getting quite old. Perhaps you could drop support for versions older than 1.509?
Currently, based on Jan 2014's stats of Jenkins installations
55% are 1.532+
80% are 1.509+
90% are 1.480+
93% are 1.466+
97% are 1.447+
99% are 1.424+
Given that this seems to be a bug in older versions of Jenkins (i.e. where they were finding the wrong form element and ignoring the relative path) I think pushing a final release that requires 1.480 followed by pushing a release that requires 1.509 and has the fix is the way I would tackle this issue.
An additional data point is that the oldest version of Jenkins that you can get commercial support for is, as far as I know, based off of 1.509...