Creating tags for non core plugins?

[David Ostrovsky]

One gerrit user brought to my attention the fact that delete-project plugin

was tagged with v2.13 tag: [1].

Usually we never tag non-core plugins. The current situation raises more

questions that it answers, because now the gerrit users are confused, why

they are seeing v2.13 version in deployed plugin list, even though they

consumed the plugin from the right stable branch (stable-2.14 in this case).

* [1] https://gerrit.googlesource.com/plugins/delete-project/+/v2.13

[Luca Milanesio]

I believe we discussed the issue multiple times and the point is: one plugin can be compatible with more than one version of Gerrit.

The plugin-manager already solves the problem and "find" the compatible plugins on gerrit-ci.gerritforge.com :-)

It is hard to convince *all* the plugins' maintainers to find a common tagging paradigm :-(

Jenkins has the same problem, and the solution is there as well => plugin manager.

Luca.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.