File:  [NetBSD Developer Wiki] / wikisrc / projects / project / cvs-migration.mdwn
Revision 1.5: download - view: text, annotated - select for diffs
Mon Dec 15 21:53:57 2014 UTC (4 years, 11 months ago) by jnemeth
Branches: MAIN
CVS tags: HEAD
- tyop
- more questions about branches

[[!template id=project

title="CVS Migration for NetBSD repos"



NetBSD is one of the first projects to use internet-available source control.
It has been using CVS since the very beginning of the project (over 21 years)
and the repository is vast.

NetBSD also hosts the pkgsrc repository which has many small files, many
"imports" and other technical challenges associated with VCS.

NetBSD also has various small internal repositories (like this wiki).

During the last twenty years tooling has improved the popular developer culture
has shifted to new workflows.

The purpose of this project is to identify:

 * existing 'workflows' in common use among developers
    * (example): [users/dholland/hgnb](/users/dholland/hgnb)
 * existing 'tooling' within NetBSD the organization
    * how much memory/disk is required to host NetBSD?
    * how are backups performed?
 * security requirements like
    * how do we validate commits?
    * how do we ensure commits originated from developers?
 * release engineering requirements such as
    * how does a pullup request work?
    * how do we ensure the correct files are included in the correct release branches?
    * how do we checkout a release branch
    * how do we look at the history of a release branch
    * how do we get different revisions of a file on a branch

major parts of the technical work like "how to convert FROM CVS to git/hg/fossil"
has already been done, which is why we are able to now ask "how would the project
continue to function?"


CVSweb for NetBSD wikisrc <> software: FreeBSD-CVSweb