Closed schmunk42 closed 4 years ago
The vast majority of issues were from 5 years ago when it was being actively developed, and the recent ones were all mistakes for swarmkit, other than some issues I resolved. Many were issues in components or Moby or other software and may be resolved. It is GitHubs (reasonable) recommendation that you close issues and PRs before archiving a repository so that people know they are not being worked on, and I was also looking to see if anyone came forward to say that they were still working on things or, indeed, actively using Swarm Classic.
As per #2986 this project is going to be archived.
Surely not all were for
swarmkit
and even if you are going to deprecateclassicswarm
it makes no sense to just close all issues, so what's the rationale behind this action?