> > We have maven and maven2 for no good reason, so the latter is on the kill > list as well. > maven2 => maven-plugin
> hudson-logaction and logaction seem to be the same component, so one must > go. > logaction-plugin is a proper name > 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. > I've created the additional section for "abstract" components, which require complex actions (security, concurrent-build, ant, etc.). Currently, the section include only "cli" and "core" components - 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 > Removed the slave-setup entry - 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 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. > It makes sense to re-work the text and put it on the Wiki page. The text should be placed on https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking after the workflow modification. I also think that somebody should describe required infrastructure changes and create appropriate INFRA issues. Examples: - Create JIRA components according to GitHub repository names instead of the plugin IDs - IRC Bot (?): Ensure that new plugin repositories have the "-plugin" suffix - ... Best regards, Oleg Nenashev пятница, 6 июня 2014 г., 5:56:51 UTC+4 пользователь Kohsuke Kawaguchi написал: > > > I think the "Untriaged" state part needs more explanation and attention, > because the intention behind this change is to encourage core&plugin > developers to change the workflow. > > The idea is that issues in this state is not confirmed/accepted by > developers. I think the expectation is that developers would go through > untriaged issues quickly and check if they seem to contain enough > information (if not, close it and let the submitter reopen with more > info), if it's filed against the right component (if not, reclassify), > etc. And if it appears to be a serious issue, we want to flag it and > make sure it gets worked on in a timely manner. > > To me, a part of the motivation for this new state is that it lets us > ensure that issues are "touched" and notice serious issues sooner than > later. This is a metric we can track to identify plugins that need love, > and measure how far behind we've fallen in the core. > > > > On 06/04/2014 11:41 AM, Oleg Nenashev wrote: > > Hello, > > > > This is a follow-up to the discussion of Jenkins JIRA issues (IRC, > > #jenkins, May 28th). > > > > I've created a page on Jenkins Wiki, which aggregates all discussed > > proposals. > > URL: > > > https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring > > > > This page is a publicly accessible draft. > > > > Any additional comments and proposals will be appreciated. > > > > Best regards, > > Oleg Nenashev > > > > -- > > 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] <javascript:> > > <mailto:[email protected] <javascript:>>. > > For more options, visit https://groups.google.com/d/optout. > > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Jenkins Enterprise, our professional version of Jenkins > -- 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.
