repository_history - ryzom/ryzomcore GitHub Wiki


title: Repository History description: published: true date: 2023-03-01T05:16:07.053Z tags: editor: markdown dateCreated: 2022-03-06T04:11:09.200Z

The original NeL CVS was a subset of the Ryzom CVS used at Nevrax. This subset forked to OpenNeL. A subset of the full repository was brought in when the project renamed to Ryzom Core. A private fork for the server was kept by Winch Gate for some time, which remains as a separate server repository that complicates merges.

@startuml node "NeL CVS (2001 to March 2007)" as NeLCVS node "Ryzom CVS (2001 to 2007 or 2008)" as RyzomCVS RyzomCVS -l-> NeLCVS node "OpenNeL SVN (July 2007 to August 2008)" as OpenNeLSVN NeLCVS -d-> OpenNeLSVN node "NeL Community (GPLv2) and Ryzom Private SVN (August 2008 to May 2010)" as NeLSVN OpenNeLSVN -r-> NeLSVN RyzomCVS --d-> NeLSVN node "Ryzom Core Hg (AGPLv3) (May 2010 and on)" as RyzomCoreHg node "Ryzom Private SVN (up to October 2012)" as RyzomSVN NeLSVN -d-> RyzomCoreHg NeLSVN -d-> RyzomSVN node "Ryzom Private Server Hg (was in violation of AGPLv3 until made public)" as RyzomServerHg RyzomSVN -d-> RyzomServerHg RyzomCoreHg ...-r-> RyzomServerHg node "Ryzom Core Git" as RyzomCoreGit node "Ryzom Forge Server Git" as RyzomForgeServerGit RyzomCoreHg --d-> RyzomCoreGit RyzomServerHg -d-> RyzomForgeServerGit RyzomForgeServerGit ...-l-> RyzomCoreGit @enduml

Revision history was unfortunately not retained during the transition from CVS to SVN, and during the transition from SVN to Mercurial. The revision history from Mercurial is retained in the current Git repository.

Currently, the Ryzom Core repository contains everything, but the separate Server repository is still being used by Winch Gate for some stupid reasons, so we have to merge in their changes manually every so often.

Ryzom Core is upstream from the commercial Ryzom game in the repository commit hierarchy. Commit branches based on the downstream commercial Ryzom fork will generally not make it into the open source release without significant efforts. Changes based on the latest Ryzom Core 4 branch (core4) can be merged into the commercial game directly (using the feature/core4-atys merging branch).

Archives

  • NeL CVS: A complete Nevrax NeL CVS archive dated March 2007 is available. A full checkout of the shader branch is available as well, and may be more recent.

  • Ryzom CVS: Not available. A private copy should still exist with someone at Winch Gate, unless they didn't keep it.

  • OpenNeL SVN: A complete backup has been recovered by the SourceForge Support and Engineering teams. It is available at the SourceForge NeL Project page. An archival Git conversion of the OpenNeL repository is available too.

  • NeL SVN: Deleted by Ulukyn from the old web server, view the web index at IA, and other revision logs at IA. A backup exists of revision 1, 170 (initial publishing), and 2459 (before the Ryzom Core transition). No revision history retained. Complete copy may exist at any SVN monitoring websites, if they happen to keep backups. A partial copy up to revision 1651 exists on Gitorious. NeL SVN Revision Logs.

    i have no any backups, before i update the configuration, servers are backuped locally and when moved from old web server to new one, we swicth to mercurial, so it's probably the same than the current ones

    The NeL SVN inherits from the Ryzom CVS, and merges in the changes from OpenNeL at several points.

  • Ryzom Private SVN: A private complete backup of revision 1 and 5143 (the last revision) exists. No known backup of the complete revision history exists. Some revision history is retained in the Ryzom Server Hg and Git repository. Whoever converted this to the private / server Mercurial might have had an SVN dump at some point. This is the same repository as the NeL SVN with additional access to a private ryzom folder.

All NeL code pre-dating the Ryzom Core repository (i.e., the NeL CVS, OpenNeL SVN, and NeL SVN) is under the GPLv2 license. The AGPLv3 applies only to code developed since the Ryzom Core transition.

See Also

⚠️ **GitHub.com Fallback** ⚠️