|
version 1.2, 2015/01/17 20:39:17
|
version 1.6, 2015/01/18 17:57:21
|
|
Line 37 project will be different and what they'
|
Line 37 project will be different and what they'
|
| This includes not just user-facing things like commit procedures but |
This includes not just user-facing things like commit procedures but |
| also backend considerations and administration. |
also backend considerations and administration. |
| |
|
| There's a [[second page|hgtodo.mdwn]] with a list of work that needs |
There's a [[second page|hgtodo]] with a list of work that needs |
| to be done. |
to be done. |
| |
|
| ### Issues |
### Issues |
|
Line 50 Technical concerns (demands on the syste
|
Line 50 Technical concerns (demands on the syste
|
| * numbered versions |
* numbered versions |
| * branch handling |
* branch handling |
| * tag handling |
* tag handling |
| * partial checkouts |
* partial checkouts (partial trees, partial history) |
| ** partial trees |
|
| ** partial history |
|
| * blacklist extension (which is a legal requirement) |
* blacklist extension (which is a legal requirement) |
| * being able to migrate away in the future |
* being able to migrate away in the future |
| * ... |
* ... |
| |
|
| Conversion of CVS repository phenomena |
Conversion of CVS repository phenomena |
| |
|
| * vendor branches |
* vendor branches |
| * conversion of repo-copies and similar CVS horrors |
* conversion of repo-copies and similar CVS horrors |
| * adding rename metadata to already-done moves |
* adding rename metadata to already-done moves |
|
Line 66 Conversion of CVS repository phenomena
|
Line 65 Conversion of CVS repository phenomena
|
| * non-ascii text in log messages |
* non-ascii text in log messages |
| * version references in log messages |
* version references in log messages |
| * retaining CVS file version numbers as metadata |
* retaining CVS file version numbers as metadata |
| * restoring the pre-settlement history and/or including the CSRG history |
* restoring the pre-USL-settlement history and/or including the CSRG history |
| |
|
| Implementation concerns (demands on the system as it exists) |
Implementation concerns (demands on the system as it exists) |
| |
|
| * general performance |
* general performance |
| * importing into base, or not |
* importing into base, or not |
| * storage requirements vs. small systems |
* storage requirements vs. small systems |
|
Line 77 Implementation concerns (demands on the
|
Line 77 Implementation concerns (demands on the
|
| * ... |
* ... |
| |
|
| Community deployment issues |
Community deployment issues |
| |
|
| * what becomes of anoncvs |
* what becomes of anoncvs |
| * making use of version numbers in mailing lists / security advisories |
* making use of version numbers in mailing lists / security advisories |
| * patches/contributions/commits from non-developers |
* patches/contributions/commits from non-developers |
| * collaborating with non-developers |
* collaborating with non-developers |
| |
|
| Developer deployment issues |
Developer deployment issues |
| |
|
| * commit procedures |
* commit procedures |
| * development branch procedures |
* development branch procedures |
| * vendor branch procedures |
* vendor branch procedures |
|
Line 92 Developer deployment issues
|
Line 94 Developer deployment issues
|
| * how to refer to other commits in log messages |
* how to refer to other commits in log messages |
| |
|
| Many of these issues are already documented in [[the existing |
Many of these issues are already documented in [[the existing |
| workflows writeup|hgnb.mdwn]]. |
workflows writeup|hgnb]]. |
| |
|
| Releng deployment issues |
Releng deployment issues |
| |
|
| * changes to the way pullups are filed |
* changes to the way pullups are filed |
| |
* adjusting processing scripts for new source-changes format |
| * release commit procedures |
* release commit procedures |
| * release branch procedures |
* release branch procedures |
| * dealing with accidental commits to release branches |
* dealing with accidental commits to release branches |
|
Line 105 Releng deployment issues
|
Line 109 Releng deployment issues
|
| * ... |
* ... |
| |
|
| Backend/admins deployment issues |
Backend/admins deployment issues |
| |
|
| |
* how commits get pushed to the master tree |
| * log_accum / source-changes mails |
* log_accum / source-changes mails |
| * access control for whole trees |
* access control for whole trees |
| * access control for subsections of trees |
* access control for subsections of trees |
|
Line 113 Backend/admins deployment issues
|
Line 119 Backend/admins deployment issues
|
| * ... |
* ... |
| |
|
| cvs assumptions / scripted usage in the tree |
cvs assumptions / scripted usage in the tree |
| |
|
| * pkgsrc: changes-entry and commit-changes-entry |
* pkgsrc: changes-entry and commit-changes-entry |
| * pkgsrc: guide regen |
* pkgsrc: guide regen |
| * ... |
* ... |
| |
|
| Other questions |
Other questions |
| |
|
| * running live in parallel with CVS during a transition period |
* running live in parallel with CVS during a transition period |
| * gatewaying to other VCS frontends |
* gatewaying to other VCS frontends |
| |
|
![[BACK]](/icons/back.gif){kind=icon}
Return to hgpath.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc / users / dholland