--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/luOqm4Qj4sc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We have maven and maven2 for no good reason, so the latter is on the kill list as well.
hudson-logaction and logaction seem to be the same component, so one must go.
Also provided a list of all non-plugin components not currently scheduled to be changed, more as a reference for further component murder than any particular desire to not see them modified.
- slave-setup was a false positive, it's a plugin (the one I actually meant when I suggested 'master-slave' as an example for a plugin component not looking like a plugin in IRC during the meeting a while back!).
- added the XXX to XXX-plugin component rename suggestion
- I added a list of plugin components missing the usual comment to indicate they're a plugin. This might well be obsolete with the "-plugin" rename, in which case all plugin components should have their (then redundant) descriptions removed to keep the components list clean (and a description should be mandatory for all components that aren't plugins).
I think the "Untriaged" state part needs more explanation and attention,
.... This is a metric we can track to identify plugins that need love,
and measure how far behind we've fallen in the core.
> <mailto:jenkinsci-dev+unsub...@googlegroups.com>.
To rename a github repo, you can just fork it to a new name within the same org. I did this with the emailext - template - plugin.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
Ant is not in a plugin, so renaming 'ant' to 'ant-plugin' would just be confusing. The same applies to 'cli' -- they are both (currently) part of jenkins.war, so should probably be merged into 'core'.
Also, GitHub repos can be renamed -- I've done it. Is there a restriction (e.g. only repos that are not yet an certain age, or not too popular, ...) or why do you write we cannot do that?
git clone
, git fetch
, or git push
operations targeting the previous location will continue to function as if made on the new location" (https://help.github.com/articles/renaming-a-repository). Seems that renaming is safe for users and automation flows. We could try the renaming on several unpopular plugins like junit-realtime-test-reporter.Ant is not in a plugin, so renaming 'ant' to 'ant-plugin' would just be confusing. The same applies to 'cli' -- they are both (currently) part of jenkins.war, so should probably be merged into 'core'.
That's about Jira, not Github. It seems that plugin component names in Jira by convention have a description containing 'plugin', see https://issues.jenkins-ci.org/browse/JENKINS#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel -- but some are exceptions, and that's what that is about.
>> - I added a list of plugin components missing the usual comment to indicate they're a plugin. This might well be obsolete with the "-plugin" rename, in which case all plugin components should have their (then redundant) descriptions removed to keep the components list clean (and a description should be mandatory for all components that aren't plugins).
> Thanks! Unfortunately, we cannot just rename GitHub repositories
Also, GitHub repos can be renamed -- I've done it. Is there a restriction (e.g. only repos that are not yet an certain age, or not too popular, ...) or why do you write we cannot do that?
We should also look into changing the description, as it specifically refers to security issues (as does 'Fix Prepared'). No idea whether this is configurable.
> I think the "Untriaged" state part needs more explanation and attention,
> .... This is a metric we can track to identify plugins that need love,
> and measure how far behind we've fallen in the core.
> * IRC Bot (?): Ensure that new plugin repositories have the "-plugin" suffix
Probably sufficient to add a note on http://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot how to name plugin repos.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/luOqm4Qj4sc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
Best regards, Oleg Nenashev
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
Best regards, Oleg Nenashev
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
"Important: This issue tracker is intended to track bugs and enhancements to Jenkins. Questions regarding configuration and operation of Jenkins should be directed towards jenkinsci-users@googlegroups.com or the #jenkins channel (http://jenkins-ci.org/content/chat) on IRC."
Regards
Richard
--
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+unsubscribe@googlegroups.com.