Updates to CollabNet TeamForge plugin

[bra...@collab.net]

My name is Ben Ravago and I work with the CollabNet Professional Services team.  We have developed a new jenkins plugin that supports the currrent version of CTF (7.x) and would like to take over maintenance of the CollabNet plugin listed on the jenkins web site (which is quite out of date).  Can you provide guidance on what I need to do to get this going?

Thanks,
Ben Ravago

[Daniel Beck]

(Moving this back to the dev list)

Ben,

The process for taking over maintainership should be relatively straightforward (modulo your emails getting lost again). The plugin appears to be mostly abandoned, but to be sure, maybe contact John McNally who is the closest we have to a current maintainer?

Could you explain a bit what your plans are for the CollabNet plugin? It looks like you want to release your plugin as a new version of the existing one that is incompatible, breaking current users' installations. Maybe there's some migration code you could include?

Daniel

On 07.07.2015, at 18:22, Benjamin Ravago <bra...@collab.net> wrote:

> Daniel,
> Thanks for the reply. Yes, I am definitely still interested in taking over maintainership of the plugin. I would have followed up sooner but we were having our own set of (distracting) internal turnovers. If there's a process to be followed, please let me know about it so I can present this to our team and get it on our schedule.
>
> Regards,
> Ben
>
> On Tue, Jul 7, 2015 at 12:07 PM, Daniel Beck <m...@beckweb.net> wrote:
> Hi Ben,
>
> I just saw this email and it appears you never got an answer. (In such cases, it helps to re-send the request.) Are you still interested in taking over maintainership?
>
> Daniel

> > --
> > 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-de...@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e4361694-f22d-461d-98c5-cc30973a3ed9%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>

[Daniel Beck]

Does it make sense to use a different plugin ID then, so your new plugin does not get offered as update to existing users? Even with the compatibility warning we could add in the plugin metadata, it'll just spam the old data monitor.

We can also deprecate the existing plugin so it won't show up in the update center anymore if it's no longer useful to new users. I don't know your product, you can better judge whether that plugin still has an audience.

On 08.07.2015, at 16:42, Benjamin Ravago <bra...@collab.net> wrote:

> Daniel,

> OK. I'll contact John McNally about it.
>
> As to plans: yes, we basically plan to replace the whole plugin. We've been distributing a re-written plugin for quite a while to our customers as the plugin on the jenkins site has not been updated since ctf 6 (we're now soon to release 8.1). We don't really have a migration path as we believe that if anyone is still using the old version, then they must be using an old (and similarly unsupported) ctf version as well and migrations in these cases tend to be highly 'customized' anyway.