Is the release not showing up? > Am 23.01.2015 um 16:15 schrieb Michael Patel <[email protected]>: > > Ok. Released ... what happens now :) ? > > On Thursday, 22 January 2015 12:33:23 UTC, Ullrich Hafner wrote: > Done. Welcome aboard! Ulli > >> Am 22.01.2015 um 11:44 schrieb Michael Patel <[email protected] >> <javascript:>>: >> >> Almost a week now with no reply. Could I maybe get commit access. >> >> Mike. >> >> On Friday, 16 January 2015 10:38:41 UTC, Michael Patel wrote: >> Pull Request created. I've pinged a mail of to joach. who is the maintainer >> of the project. If I don't hear back would it be possible to get commit >> access to merge my changes in ? >> >> https://github.com/jenkinsci/graphite-plugin/pull/4 >> <https://github.com/jenkinsci/graphite-plugin/pull/4> >> >> MP >> >> On Monday, 12 January 2015 11:22:29 UTC, Ullrich Hafner wrote: >> After your PR is integrated into >> https://github.com/jenkinsci/graphite-plugin >> <https://github.com/jenkinsci/graphite-plugin> you need to run the release >> command for this repository. In your fork you only change the source code >> for the fixes, the URLs remain the same as they are... >> >>> Am 12.01.2015 um 09:25 schrieb Michael Patel <[email protected] <>>: >>> >>> Further question, >>> >>> Currently i'm proceeding as advised, but i'm a little confused. The >>> distribution management url configuration for the project is currently set >>> to http://maven.jenkins-ci.org:8081/content/repositories/releases/ >>> <http://maven.jenkins-ci.org:8081/content/repositories/releases/> >>> >>> I'm confused as to whether to maven release on my fork and merge or merge >>> and then release on the jenkins repo itself ? >>> >>> Which is the correct approach ? >>> >>> MP >>> >>> On Friday, 9 January 2015 16:42:34 UTC, Michael Patel wrote: >>> Great, will do. >>> >>> I'll contact the author aswell jic. >>> >>> On Friday, 9 January 2015 16:26:02 UTC, Ullrich Hafner wrote: >>> >>>> Am 09.01.2015 um 17:12 schrieb Michael Patel <[email protected] <>>: >>>> >>>> Hi guys, >>>> >>>> I've noticed that the graphite plugin >>>> https://github.com/jenkinsci/graphite-plugin >>>> <https://github.com/jenkinsci/graphite-plugin> to send metrics to jenkins >>>> is currently inactive pending the 1.2 release. >>>> >>>> The 1.1 release no longer works as the api to get test results has changed >>>> slightly. >>>> >>>> I'm happy to release from our organization's fork and to add in some extra >>>> metrics going forward. >>>> >>>> github username : patelm5 >>>> plugin name : graphite-plugin-fork >>>> fork : https://github.com/betgenius/graphite-plugin >>>> <https://github.com/betgenius/graphite-plugin> >>>> >>>> Is this the correct way to go about reviving zombie projects ? >>> >>> Actually no. We recommend to integrate your changes as pull request in the >>> existing plug-in. We can give you commit rights so you can integrate these >>> changes on your own (seems that the irc bot currently is down). >>> And if there is no active maintainer anymore (did you contact the authors?) >>> then you can take over the ownership of the plugin… >>> >>>> >>>> Cheers, >>>> MP >>>> >>>> >>>> -- >>>> 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] <>. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/604d43d5-a7f6-4080-9e7c-e830e0871175%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/604d43d5-a7f6-4080-9e7c-e830e0871175%40googlegroups.com?utm_medium=email&utm_source=footer>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> 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] <>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/17d247fb-6c7a-4656-8f24-305aa8e5f227%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/17d247fb-6c7a-4656-8f24-305aa8e5f227%40googlegroups.com?utm_medium=email&utm_source=footer>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> 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:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/07c1a15e-c63f-491c-b22b-b60c9fc7dc20%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/07c1a15e-c63f-491c-b22b-b60c9fc7dc20%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/62f16345-140f-43d0-a447-bbcd4a44d589%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/62f16345-140f-43d0-a447-bbcd4a44d589%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>.
-- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/10009C8B-D8A2-4A0D-BE3A-994C74C9A925%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
