Hi, team. I have noticed that there's a lot of maintenance still going on for providers that are not only in labs, but haven't had any feature work in over a year. Some of these are in fact dead and could be removed. Others are far behind in versions. In any case, providers with no owner or live tests run are simply tech debt.
Here's a suggestion for a start. unhook aging code such as the jenkins, virtualbox, savvis, etc providers from master. keep them in 1.8.x branch, and keep that compiling, but don't release them in 2.x Later, we can suggest a process for a real attic -> /dev/null for things that are "not quite dead, yet" The thing is, that if there's a provider that hasn't been touched in over a year, it needs a significant helping of work to refactor into current approach, and nothing in labs should exit as an antique anyway. Meanwhile this frees us up to modernize core, such as removing async, etc. At the end of the day, we need to be able to both start and complete hard things. Labs providers, especially orphaned ones, shouldn't get in the way of the latter. Thoughts? -A
