I think it's all done on my side.
On 03/08/2013 11:11 AM, Andrei Pozolotin wrote:
lets do the following: 1) I will make plug-in maven coordinates as follows: <groupId>com.barchart.jenkins</groupId> <artifactId>maven-release-cascade</artifactId> 2) I will make plug-in jenkins runtime URL to match artifact id: http://.../maven-release-cascade/... 3) we will keep github repo, etc, on barchart side follow our current pattern: https://github.com/barchart/barchart-jenkins-cascade-plugin 4) you will make https://github.com/jenkinsci/barchart-cascade-plugin into https://github.com/jenkinsci/ <https://github.com/jenkinsci/barchart-cascade-plugin>maven-release-cascade 5) and you will make everything else on jenkins/cloudbees side look like http://.../maven-release-cascade I committed proposed changes. https://github.com/jenkinsci/barchart-cascade-plugin what do you think? On Friday, March 8, 2013 12:36:50 PM UTC-6, Kohsuke Kawaguchi wrote: On 03/08/2013 10:06 AM, Andrei Pozolotin wrote: > Kohsuke: > > great, thanks for the setup. > > is plugin maven artifactId name change enough or do you need github > repository name change as well? I can make the repository name change for you. Having two things match is probably easier. If you are OK with what I'm proposing, I'm happy to make the changes, and create the rest of the stuff (BuildHive, JIRA, etc.) > Thank you. > > Andrei. > > > On Friday, March 8, 2013 11:59:15 AM UTC-6, Kohsuke Kawaguchi wrote: > > > Thanks! I forked it into > https://github.com/jenkinsci/barchart-cascade-plugin/ <https://github.com/jenkinsci/barchart-cascade-plugin/> > <https://github.com/jenkinsci/barchart-cascade-plugin/ <https://github.com/jenkinsci/barchart-cascade-plugin/>> > > You also should have commit access. > > There's a couple of comments around the plugin name. > > First, it is customary to remove "-plugin" from the artifact ID name. I > strongly recommend this to keep it in line with other plugins. > > > I also wonder if the plugin would be better renamed as > "maven-release-cascade" as opposed to "barchart-jenkins-cascade" to > better convey what it does. I first thought "Barchart" refers the > specific type of charts, and so I assumed this was a plugin that > generates some kind of bar charts. > > Upon reading it further, I see that barchart is your company name, and > this plugin is actually around the maven release process. So I think > "maven-release-cascade" better represents what it does. > > For ways to receive due credit for Barchart.com, Inc., I think of > [1] as > the current common practice. > > > > [1] https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin <https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin> > <https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin <https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin>> > > On 03/07/2013 05:45 AM, Andrei Pozolotin wrote: > > Kohsuke Kawaguchi, hello. > > > > This is a plugin hosting request. > > > > 1) We are getting ready for the first release of the plugin, please > > setup a fork: > > https://github.com/barchart/barchart-jenkins-cascade-plugin <https://github.com/barchart/barchart-jenkins-cascade-plugin> > <https://github.com/barchart/barchart-jenkins-cascade-plugin <https://github.com/barchart/barchart-jenkins-cascade-plugin>> > > > > 2) Please setup a build hive account/project for this pluign: > > https://buildhive.cloudbees.com/job/jenkinsci/ <https://buildhive.cloudbees.com/job/jenkinsci/> > <https://buildhive.cloudbees.com/job/jenkinsci/ <https://buildhive.cloudbees.com/job/jenkinsci/>> > > > > 3) My github account: > > https://github.com/Andrei-Pozolotin <https://github.com/Andrei-Pozolotin> > <https://github.com/Andrei-Pozolotin <https://github.com/Andrei-Pozolotin>> > > > > 4) My jenkins jira account > > https://issues.jenkins-ci.org/secure/ViewProfile.jspa <https://issues.jenkins-ci.org/secure/ViewProfile.jspa> > <https://issues.jenkins-ci.org/secure/ViewProfile.jspa <https://issues.jenkins-ci.org/secure/ViewProfile.jspa>> > > andrei_pozolotin > > > > Thank you. > > > > Andrei. > > > > -- > > 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] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out <https://groups.google.com/groups/opt_out> > <https://groups.google.com/groups/opt_out <https://groups.google.com/groups/opt_out>>. > > > > > > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Nectar, our professional version of Jenkins > > -- > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out <https://groups.google.com/groups/opt_out>. > > -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins -- 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.
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins -- 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.
