mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

minor tweaks to transition plan

Browse source
This commit is contained in:
Joey Hess 2019-02-20 11:28:00 -04:00
parent 728228d5d2
commit 2f67c4ac87
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

32
doc/todo/v7_path_toward_default.mdwn
View file

@ -6,9 +6,10 @@ done
## step 2: default for new direct mode repositories ## step 2: default for new direct mode repositories
Done when using the command line. The assistant still creates direct mode Done when using the command line to init in a crippled filesystem.
repositories though, and will need to enable annex.thin and adjusted
unlocked branch instead. The assistant still creates direct mode repositories though,
and will need to enable annex.thin and adjusted unlocked branch instead.
## step 3: auto-upgrade from direct mode ## step 3: auto-upgrade from direct mode
@ -23,11 +24,17 @@ Here are some problems that need to be investigated first:
- <http://git-annex.branchable.com/bugs/v6_appears_to_not_thin/> - <http://git-annex.branchable.com/bugs/v6_appears_to_not_thin/>
- <http://git-annex.branchable.com/bugs/git-annex-sync_sometimes_fails_in_submodule_in_V6_adjusted_branch/> - <http://git-annex.branchable.com/bugs/git-annex-sync_sometimes_fails_in_submodule_in_V6_adjusted_branch/>
Also need to wait until git-annex v7 is widely supported. In Debian stable Note that direct mode repos with old git-annex interoperate with adjusted
seems reasonable. A direct mode repository may be used by multiple unlocked repos with new git-annex, so there is no need to wait for v7 to be
machines, some not supporting v7 and some that do. widely supported.
## step 4: automatic v5 to v7 upgrades ## step 4: default for all new repositories
Could probably happen fairly soon after default in direct mode.
This is entirely new repositories that git-annex init is run in for the
first time (no sibling git-annex branches).
## step 5: automatic v5 to v7 upgrades
Since v5 repos and v7 repos not using unlocked files are functionally Since v5 repos and v7 repos not using unlocked files are functionally
almost identical, this is unlikely to break much. Unlocking files will of almost identical, this is unlikely to break much. Unlocking files will of
@ -35,18 +42,15 @@ course change behavior though.
This needs to be deferred until every git-annex likely to be in use This needs to be deferred until every git-annex likely to be in use
supports v7. A v5 repository may be used by multiple supports v7. A v5 repository may be used by multiple
machines, some not supporting v7 and some that do. Probably around the same machines, some not supporting v7 and some that do. If one upgrades to v7
time auto-upgrade from direct mode is done then. and starts using unlocked files, those files won't be accessible on the old
v5 machines.
## step 5: default for all new repositories
Could probably happen fairly soon after default in direct mode.
## step 6: remove support for direct mode ## step 6: remove support for direct mode
Will simplify a lot of code. Will simplify a lot of code.
## step 6: remove support for v5 ## step 7: remove support for v5
This won't simplify much code, but maybe worth doing eventually. This won't simplify much code, but maybe worth doing eventually.
Best not to rush this, maybe in 5 years from when v7 is default? Best not to rush this, maybe in 5 years from when v7 is default?