1 |
Re-posting for discussion on gentoo-scm (apologies if this is a dupe, |
2 |
but I'm pretty sure I wasn't subscribed for the last attempt): |
3 |
|
4 |
Looking at the tracker [1], we need a pre-upload hook (I'm not quite |
5 |
sure why), an rsync conversion script, the ability to validate the |
6 |
converted tree, and documentation. There is still an open bug for |
7 |
commit signing, and I'm not quite sure why as this was implemented. |
8 |
|
9 |
It seems like a lot has already been done with validation. Checking |
10 |
the active tree is pretty trivial - just compare the trees and they |
11 |
should be the same. I guess we need to check history, but it seems to |
12 |
me like the risk of problems is low, and if we just keep a backup of |
13 |
the cvs repository if there is ever a concern about who made some |
14 |
commit 5 years ago we can always dig it up. |
15 |
|
16 |
It really seems to me like little remains to be done here. Mostly we |
17 |
just need somebody to push a decision on things like workflow. A few |
18 |
of the bugs have comments like "no sense working on this with other |
19 |
stuff still needed" - which seems to be outdated thinking with so |
20 |
little left to do. |
21 |
|
22 |
Am I missing some big concern that just isn't obvious in these bugs? |
23 |
|
24 |
I also fear that we're refusing to take action on a great solution |
25 |
because it isn't a perfect solution. Nobody in the world is using |
26 |
tree-signing with git, and we aren't really using it in cvs either. |
27 |
We now have the ability to do it with git, but depending on workflow |
28 |
3rd-party signatures might not end up in the history of head, or we |
29 |
might not be able to verify them in an automated fashion. Honestly, I |
30 |
think the appropriate response here is whoop-de-doo. We can't do any |
31 |
of that stuff with cvs, but moving to git would have a lot of other |
32 |
benefits. We can always change our processes later once somebody has |
33 |
a solution for the signing problem. Right now we're making do without |
34 |
it on cvs, and so is every other project using git. We can also |
35 |
continue to sign manifests as a workaround, which is what we'll be |
36 |
doing anyway if we never migrate to git. |
37 |
|
38 |
The git migration just strikes me as one of those cases where anybody |
39 |
is free to come up with a reason not to use something, but nobody has |
40 |
to defend keeping the status quo. I think the question isn't whether |
41 |
there is anything wrong with using git, but whether the problems with |
42 |
git are worse than the problems we already have. |
43 |
|
44 |
Rich |
45 |
|
46 |
[1] - https://bugs.gentoo.org/show_bug.cgi?id=333531 |