As result we (patbos and me): - released two versions with 3 fixes. - fixed selenium tests and added a test case for one reverted commit that broke master (it can be reopened for better review). - added changelog (that absent before) to wiki page. I very hope that real maintainers will appear, continue resolving jira issues and provide right contacts. This should unblock some users and prevent jenkins from broken state.
On Thursday, March 12, 2015 at 3:11:15 AM UTC+3, Kanstantsin Shautsou wrote: > > Hi, i think this plugin suffers from retired authors/maintainers. Last > time i did merge+release after they didn't reply to maillist/contacts. As i > see some of them already merged two PR, but not released. I see that many > people hit this bug so i can help with revewing/testing/merging/releasing > again. Please contact me in IRC tomorrow and let's try decide what to do. > > On Wednesday, January 21, 2015 at 11:30:34 AM UTC+3, pat...@patbos.com > wrote: >> >> Hi, >> >> I have created a PR for the build-pipeline-plugin with fixes for >> JENKINS-22665 and JENKINS-19755. >> https://github.com/jenkinsci/build-pipeline-plugin/pull/64 >> >> The PR will solve problem with the serialization of the User object >> within MyUserIdCause (JENKINS-22665) and after a restart all manual >> triggers will not show the user and just show anonymous (JENKINS-19755). >> This is a big problem for our Jenkins installation >> >> Can a committer of the plugin please review and merge this PR? >> >> Regards >> Patrik Boström >> > -- 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/286fa45b-5292-402f-a288-2953a41bfe8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
