Hi guys, I was at one point the maintainer of the plugin, though I wasn't very active at all. The job I was at had AccuRev, but I have since moved on to a different employer, and so I no longer have any access to AccuRev to work on it. If someone else would like to take up this mantle, I could pass on ownership of tickets and such. I don't feel comfortable doing any releases myself at this point without an actual AccuRev instance to test with.
I'm back in the svn world, and working on a move to git. I gotta say it feels kind of good to be back on the other side. :) But if anyone has any questions about working on that code, I'll provide what info I know. I need to give Jenkins some love - it makes my life easier every day after all. -Scott On Sat, Aug 3, 2013 at 10:45 AM, Ulli Hafner <[email protected]>wrote: > Actually, sending a pull request would be the best way… > https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories > > Ulli > > Am 03.08.2013 um 17:19 schrieb Raymond Munian <[email protected]>: > > I submitted a patch for > JENKINS-13406<https://issues.jenkins-ci.org/browse/JENKINS-13406> by > attaching the patch based on instructions I found in another post. Is this > the correct process? I am not sure if someone is actively maintaining the > plugin. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
