buildtriggerbadge Jira component created for batmat,
but ... your plugin has no bug, has it ? 2012/9/21 Baptiste MATHUS <[email protected]> > Hi, > The corresponding component is missing on JIRA. I suppose it's not created > automatically? > > Could it be created or could I get the rights to do it > (pluginId=buildtriggerbadge, JIRA username=batmat)? > > Thanks a lot. > Cheers > > 2012/9/18 Baptiste MATHUS <[email protected]> > >> >> >> 2012/9/18 nicolas de loof <[email protected]> >> >>> By the way, I've had a look at the plugin contributors wiki pages, but >>>> didn't find the information about plugin hosting under jenkinsci github >>>> organization: >>>> >>>> 1. Are we to work on our repo, and sometimes someone having commit >>>> rights onto the jenkinsci forked is going to git pull --rebase upstream? >>>> 2. Or are we to work directly on the jenkinsci forked version? >>>> 3. What else? >>>> >>>> As you like. You can move all dev effort on jenkinci, using branches if >>> you need to experiment a few. You also can use it only as a canonical repo >>> and still use your own repo to review each-other changes before pushing. >>> It's all yours, and depends on your maturity and expectations with DVCS :) >>> >> >> OK, thanks a lot. >> Well, as read somewhere else, "I [already] crashed and burned. Badly. >> Multiple times." with Git (©KR). >> So, I guess we might consider removing upstream to prevent being unclear >> about where the reference version of the plugin is. >> Git branching + DVCS seems already quite enough when needing to >> experiment :). >> >> Cheers >> >> >> -- >> Baptiste <Batmat> MATHUS - http://batmat.net >> Save a tree, >> Eat a beaver. >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
