Wouldn’t it then make sense to combine these two plugins? Or continue the development in the old plugin? Or should the old one be dereleased afterwards?
BTW: We can’t fork a fork of a Jenkins plugin (technical reasons). You need to provide another git repository (or we create an empty one where you can commit to). Am 05.10.2014 um 12:52 schrieb Aidan McGinley <aidmc...@gmail.com>: > Hi, > > I've developed a new plugin for capturing quality metrics for a build. It's > heavily influenced by the now defunct mttr plugin > (https://github.com/jenkinsci/mttr-plugin), but different enough that it > warrants it's own space in my view. It's been generalised to be able to > capture more than just the single metric that the MTTR plugin handled. > > Plugin name: Quality Metrics Plugin > Existing repo: https://github.com/mcgin/quality-metrics-plugin > Github id: mcgin > > Thanks. > > -- > 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. > For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
