On Wed, Jan 4, 2023 at 8:53 AM Andrey Loskutov <losku...@gmx.de> wrote:
> Also for the sake of entertainment: WHERE is the not supported CVS support > code? > Is it available in some eclipse/github/gitlab repo? > https://github.com/eclipse-platform/eclipse.platform.team/issues/8 and https://github.com/eclipse-platform/eclipse.platform.team/commit/7592b18cbbb95c47723044805933c3d4298306fb are where the removal of CVS plugins took place. Anyone interested can fetch the parent commit https://github.com/eclipse-platform/eclipse.platform.team/commit/160248690da26615c80fc2e7342e4109f232452e and get the org.eclipse.team.cvs* folders to fork from. > IMHO, UX is also API Well, I don't think it's a matter of opinion here, but a matter of definition. When Eclipse Project says "API" in its retention policy, it clearly doesn't say "UX". > Presumably it was possible to write a program that re-used team CVS support to check out a CVS project. That's why the removal was announced way ahead of the actual removal, so that people who presumably cared enough could tell and ask for another process or some delay if necessary. But no-one did.
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
