Return to cvs-migration.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / projects / project

Annotation of wikisrc/projects/project/cvs-migration.mdwn, revision 1.5

1.1       mspo        1: [[!template id=project
                      2: 
                      3: title="CVS Migration for NetBSD repos"
                      4: 
                      5: contact="""
                      6: [tech-repository](mailto:tech-repository@netbsd.org)
                      7: """
                      8: 
                      9: category="misc"
                     10: difficulty="hard"
                     11: 
                     12: description="""
                     13: NetBSD is one of the first projects to use internet-available source control.
                     14: It has been using CVS since the very beginning of the project (over 21 years)
                     15: and the repository is vast.
                     16: 
                     17: NetBSD also hosts the pkgsrc repository which has many small files, many
                     18: "imports" and other technical challenges associated with VCS.
                     19: 
                     20: NetBSD also has various small internal repositories (like this wiki).
                     21: 
                     22: During the last twenty years tooling has improved the popular developer culture
                     23: has shifted to new workflows.
                     24: 
                     25: The purpose of this project is to identify:
1.3       mspo       26: 
1.2       mspo       27:  * existing 'workflows' in common use among developers
1.4       wiki       28:     * (example): [users/dholland/hgnb](/users/dholland/hgnb)
1.2       mspo       29:  * existing 'tooling' within NetBSD the organization
1.4       wiki       30:     * how much memory/disk is required to host NetBSD?
1.5     ! jnemeth    31:     * how are backups performed?
1.2       mspo       32:  * security requirements like
1.4       wiki       33:     * how do we validate commits?
                     34:     * how do we ensure commits originated from developers?
1.2       mspo       35:  * release engineering requirements such as
1.4       wiki       36:     * how does a pullup request work?
                     37:     * how do we ensure the correct files are included in the correct release branches?
1.5     ! jnemeth    38:     * how do we checkout a release branch
        !            39:     * how do we look at the history of a release branch
        !            40:     * how do we get different revisions of a file on a branch
1.1       mspo       41: 
                     42: major parts of the technical work like "how to convert FROM CVS to git/hg/fossil"
                     43: has already been done, which is why we are able to now ask "how would the project
                     44: continue to function?"
                     45: 
                     46: 
                     47: """
                     48: ]]