Would this be limited to old entries targeting old versions of Eclipse, or would you want to do cleanup of current entries which include old versions (targeting old versions of Eclipse) ?
I don’t get the (real) difference between those two yet. What is an old and what is a current entry?
Independent of that, I think you raise the question whether the marketplace should list entries for older Eclipse versions, e.g., Eclipse Juno/4.2/5 years old. That’s an interesting discussion too. But I think there is a use case for supporting that.
I only rambled about plugins that apparently have no working update site nor a normal website.
Here's a simplistic solution to the problem I raised: I propose that every solution provider should get an email by the EF (once). That email asks the provider to renew/update his marketplace solution within 30 days. If he does not do that, the marketplace entry will be disabled.
That will probably identify most inactive/unmaintained solutions quickly (and can be reversed if needed).
– Marcel
Would this be limited to old entries targeting old versions of Eclipse, or would you want to do cleanup of current entries which include old versions (targeting old versions of Eclipse) ?
For example, I recently removed the Juno- and Indigo-based versions of the JBoss Tools connector [1] because there's a hard limit on the # of features that can be displayed in a given solution listing, and because that's 4-5 year old code.
Nick
_______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
