> On Jun 9, 2015, at 16:14, Stephen Connolly <[email protected]> > wrote: > > > > On 9 June 2015 at 14:05, Baptiste Mathus <[email protected] > <mailto:[email protected]>> wrote: > > 2015-06-09 14:53 GMT+02:00 Kanstantsin Shautsou <[email protected] > <mailto:[email protected]>>: > > > On Jun 9, 2015, at 15:47, Baptiste Mathus <[email protected] > > <mailto:[email protected]>> wrote: > > > > +1 Good idea. At first before opening your full message, I thought 3 months > > for last commit would be far too limiting. But the PR idea is very cool: > > simple and to the point. The maintainer can just answer something standard > > or something at all to prevent his plugin going to the attic state. > > > > There could even be something like the process posting a second warning as > > a comment after a grace period like "It's been one month, please add a > > comment before blablabla so that that plugins isn't tagged as attic". > > > > Btw, there should also be a documented way to move a plugin out of the > > attic (either because you missed the PR, or because a plugin got new > > maintainers). > > Why end-user in update center should care about when last commit was done? If > plugin works and solves user issues - nobody cares and this label will just > confuse. Some plugins are jut libraries (like github-api plugin) and they can > be stable for long time, such PRs will look like WTF. > > End users are (typically) Jenkins admins. > I am one of those people. > I totally care about if a plugin is actually abandonned when I install it. > I always look at the number of installations, and I would definitely consider > that information and find it absolutely valuable. > > Sure, plugins may indeed not receive much modifications (for one, our BTB > plugin is a good example) because it's stable and has very few features. > But that it's not abandonned is an information indeed valuable to end user. > > > So let's take the github api plugin as an example so. > > The PR gets created. The current maintainer responds to the PR with "Don't > want to update the parent because XYZ" and that's it for another 3 months. > > We get two benefits from this: > > * We find out the plugins that have a maintainer who is pinging the project > at least once per month > * We gently nudge all the plugins to use a newer baseline (which will allow > for tidy-up of the code) > > What's not to like? Jenkins FOSS has not much resources (in comparison to CloudBees) for wasting time for such activities. github-api plugin released with kk agreement by me or oleg. But no one from us ha time for answering for spam PRs. I know projects where ISSUES can be created automatically, but not RPs. I also expect that your algorithm will spam die with master-slave changes.
New baseline why? Just because you want? Why people with older jenkins versions must loose updates (note 2-3 LTS lines may have some update blockers for users)? > > -Stephen > > -- Baptiste > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5v_KZmSvEtO0%3DOYbDSLb%2BWFiwhYTZ%3DpDTFjvExNbVt%3Dg%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5v_KZmSvEtO0%3DOYbDSLb%2BWFiwhYTZ%3DpDTFjvExNbVt%3Dg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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/Ih0RviQ0G90/unsubscribe > <https://groups.google.com/d/topic/jenkinsci-dev/Ih0RviQ0G90/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxpf0p71gLzUWRaT6QdBOu2Pv%2BYFpv5J6hM9uUJO9Oozw%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxpf0p71gLzUWRaT6QdBOu2Pv%2BYFpv5J6hM9uUJO9Oozw%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2A71F431-6C3A-4110-9CC7-0F87EE56E119%40gmail.com. For more options, visit https://groups.google.com/d/optout.
