On 06/04/2014 01:05 PM, Jesse Glick wrote:
On Wed, Jun 4, 2014 at 2:41 PM, Oleg Nenashev <[email protected]> wrote:
Any additional comments and proposals will be appreciated.
I would not make an exception to the rule that “only a single
component per GitHub repository should exist".
+1. No matter how we classify things, there will be some pain, so might
as well stick to the simplest one.
Also +1 for naming components the same as repository names. I think it
makes the automation easier, and really that's the only way to manage
900+ plugin project.
I would suggest that the JIRA component name exactly match the
repository name in all cases, specifically meaning that we should use
git-plugin rather than git, etc. (Originally I was thinking that the
plugin artifactId/shortName should match the component, but using the
repository name makes it clearer what is a plugin vs. some other
library, and gives us better consistency overall.)
hudson.sfbay is presumably obsolete, seeing as this Sun Microsystems
intranet domain no longer exists. :-)
This was what I used to track problems/tasks for my deployment called
hudson.sfbay.sun.com. So we can just close any pending issues and
consider them obsolete.
--
Kohsuke Kawaguchi http://kohsuke.org/
--
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].
For more options, visit https://groups.google.com/d/optout.
