Community
Participate
Working Groups
We need to set a date for completing the retirement of CVS at eclipse.org. In retirement, all CVS repositories will be made read-only. Projects must be completely migrated off of CVS by that date. We are currently thinking of setting that date to December 21, 2012.
Where will the train aggregation repos move to? If they will move to SVN, can we do this soon?
(In reply to comment #1) > Where will the train aggregation repos move to? > > If they will move to SVN, can we do this soon? Git is the preferred destination. SVN is on our hit list as well.
Okay, thanks.
I think the date could be more ambitious than December 2012. Why not aim for August 2012? We should also consider announcing a retirement of SVN as well, either at the same time, or one year later. There's really no reason to have either of them around in 2013.
I think that retiring cvs support should also mean removing CVS support from Eclipse default downloads - and making an optional feature pack of it. Smooth transition would require shipping Juno with both CVS and Git, and then finally removing CVS in 2013. Eclipse CVS repos could be moved to Git before Juno is shipped, and then, with next Eclipse, effectively shut down.
(In reply to comment #5) > I think that retiring cvs support should also mean removing CVS support from > Eclipse default downloads - and making an optional feature pack of it. That may also be a good idea, but there's no reason why that couldn't be done during the Juno timeframe (i.e., make it optional *now*). But more importantly, there's no reason to couple 'what Eclipse ships with' vs whether the foundation continues to support CVS.
(In reply to comment #5) > I think that retiring cvs support should also mean removing CVS support from > Eclipse default downloads - and making an optional feature pack of it. That's not unthinkable for the time after the Juno release but it is a decision of the EPP package maintainers. Maybe you can enter a new bug report against EPP to make sure that it is not forgotten... (but I am sure this issue will come up sooner or later)
Please could you confirm that we will also stop using cvs for the web site.
(In reply to comment #5) > I think that retiring cvs support should also mean removing CVS support from > Eclipse default downloads - and making an optional feature pack of it. > There is a brief discussion of this in Bug 345479 comment 4 as well as on the wiki [1]. Discussion about moving the websites is covered by Bug 324116. [1] http://wiki.eclipse.org/Platform-releng/Juno_Git_Migration#Including_eGit_in_Eclipse_SDK
(In reply to comment #8) > Please could you confirm that we will also stop using cvs for the web site. Confirmed. See Bug 324116.
What is the plan and target date to move the aggregation build files for the train? They are the only piece in CVS that I deal with on a regular basis, and the more projects are migrated the more odd it is that the callisto project (train builds) hasn't moved.
(In reply to comment #9) > (In reply to comment #5) > > I think that retiring cvs support should also mean removing CVS support from > > Eclipse default downloads - and making an optional feature pack of it. > > > > There is a brief discussion of this in Bug 345479 comment 4 as well as on the > wiki [1]. I have raised an explicit bug for the removal of CVS from the Eclipse SDK at bug 359466
Can this bug now be marked fixed?
(In reply to comment #13) > Can this bug now be marked fixed? It looks like we still have a little garbage to clean up. I'd prefer to leave this open until after we've resolved the dependent bugs.
I recall a discussion on cross-project-issues-dev where some people expected CVS to remain (in read-only state) whereas others thought it was communicated clearly that CVS repos would be deleted entirely. Before closing this bug I recommend to make a clear statement in this regard in this bug which starts: (In reply to comment #0) > We need to set a date for completing the retirement of CVS at eclipse.org. > In retirement, all CVS repositories will be made read-only. and also on http://eclipse.org/projects/scmcountdown.php: > CVS was retired at 12:00 PM EST on December 21/2012 (it has been made read-only)
Can we close this? -M.
I don't care if you close the bug, just remember we still use CVS for Orbit (read and write), and we (many of us, not just Orbit) will need read access still. But things are working fine, from my point of view, if you mean to close the bug to signify "current state" is working.
CVS is no more.
