Community
Participate
Working Groups
We stopped allowing new projects to select SVN as their repository a long time ago. The number of projects still using SVN has dropped considerably. AFAICT, we have: * 48 SVN directories under /svnroot (I'll list them in a comment) * 30 projects claim SVN repositories in their metdata I believe that many/most of these projects have already migrated to Git. We are at a point where we need to consider updating some of the tools we use internally and provide to committers (e.g. Dash). I do not, at this point, have any intention of continuing support repositories other than Git. I think it's time to deprecate SVN support officially. After further investigation (i.e. after I determine how many projects are actually using SVN), I'll take a stab at setting a date.
(In reply to comment #0) > * 48 SVN directories under /svnroot (I'll list them in a comment) I've decided not to bother listing the repositories at this point. Maybe after I prune out the bogus/unused ones...
I'd like to suggest we announce the deprecation status ASAP, and plan on a shut-down date of Dec. 22, 2014.
(In reply to Denis Roy from comment #2) > I'd like to suggest we announce the deprecation status ASAP, and plan on a > shut-down date of Dec. 22, 2014. +1
Announced to eclipse.org-committers: https://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00947.html
Having an SVN repository is important for the Subversive project. Is it possible to remain Subversive source code storing in SVN? By storing sources of SVN plug-in in SVN we use the project during its development. It allows us to find problems by ourselves and better understand needs of SVN community. In all other cases we will be glad to migrate to Git, but in our case it's important to use the project every day to develop it. Regards, Igor Vinnykov Subversive team
> Having an SVN repository is important for the Subversive project. Is it > possible to remain Subversive source code storing in SVN? By storing sources > of SVN plug-in in SVN we use the project during its development. It allows > us to find problems by ourselves and better understand needs of SVN > community. In all other cases we will be glad to migrate to Git, but in our > case it's important to use the project every day to develop it. We were expecting to hear from you :) We certainly understand your position, and we very much appreciate your willingness to use Git where it makes sense to do so. For the CVS->Git migration we've made an exception for the Orbit project, so I can certainly make an exception for the Subversive project.
Thank you for understanding, Denis. It's really important for us to use the SVN repository. We appreciate your for the decision that will allow us to use SVN in development.
Wayne, is there anything left to do here? I'm pretty sure we've successfully "Deprecated" SVN?
Movng to Subversion component.
I guess a deadline has to be set and communicated. I'm "guilty" for one of the projects - tools.mat - and we'll do the migration after the Luna release.
(In reply to Denis Roy from comment #2) > I'd like to suggest we announce the deprecation status ASAP, and plan on a > shut-down date of Dec. 22, 2014. The deadline is set. I'll communicate it in my next committers communication.
(In reply to Denis Roy from comment #11) > (In reply to Denis Roy from comment #2) > I'd like to suggest we announce > the deprecation status ASAP, and plan on a > shut-down date of Dec. 22, 2014. > The deadline is set. I'll communicate it in my next committers > communication. Sorry, need to read more carefully next time. I think end of the yeae is fair enough.
I think SVN is successfully deprecated. I'll open a follow-up bug for its removal, and to assist projects in moving.
