Possible issues for 1.5.4
https://issues.jenkins-ci.org/browse/JENKINS-38889 User configurable option for number of options displayed in Active Choices
https://issues.jenkins-ci.org/browse/JENKINS-38570 Support custom delimiters for multiselection parameters
https://issues.jenkins-ci.org/browse/JENKINS-38893 Active Choice Reactive Reference parameter value rendered as File Selector not cascaded
https://issues.jenkins-ci.org/browse/JENKINS-42655 Active choices parameters not rendering after dsl generation
https://issues.jenkins-ci.org/browse/JENKINS-39742 Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException)
https://issues.jenkins-ci.org/browse/JENKINS-39593 Performance slow in 1.5 release
https://github.com/jenkinsci/active-choices-plugin/pull/4
https://issues.jenkins-ci.org/browse/JENKINS-39442 Hidden reactive reference parameter in release build causes all parameters to be hidden
https://issues.jenkins-ci.org/browse/JENKINS-39357 Provide a paging feature for long option lists
https://issues.jenkins-ci.org/browse/JENKINS-39303 Enhance Input Text Box type for ActiveChoice Reference parameter
https://issues.jenkins-ci.org/browse/JENKINS-36158 Active choice reactive reference parameter not working on checkbox reference
https://issues.jenkins-ci.org/browse/JENKINS-35101 The selected values of checkbox reactive parameter are not available in Scriptler groovy script
https://issues.jenkins-ci.org/browse/JENKINS-34750 Reactive Parameter updating on click of itself not on change of referenced parameter
https://issues.jenkins-ci.org/browse/JENKINS-28736 DB Based choice provider
https://issues.jenkins-ci.org/browse/JENKINS-29969 groovy script can not run on node specified for the job
Query
project = JENKINS AND component = active-choices-plugin AND status not in (Resolved, Closed, "Won't Fix") AND id not in (JENKINS-41709, JENKINS-32922, JENKINS-28734, JENKINS-28735) ORDER BY assignee ASC
Vote if there are any issues you would like to see included. We can release a version with just one issue, depending on the issue, several minor issues, or cut multiple releases one after the other. Depending on what we select from this list.
Pull requests were also triaged. So the schedule for now:
* Finish triaging issues and start working on 1.5.4 next week
* Release a new version in two weeks (weekend 25/26)
* Wait for user feedback, and in the meantime update site, write blog, and triage user questions in StackOverflow, Wiki page, and check for isses created since 1.5.3
Cheers
Bruno