From b5a6dfc779080cdd147990b4c2344a9ec7fb4ea5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 31 Oct 2018 08:31:07 -0400 Subject: [PATCH] close smudge, open transition tracking item --- doc/todo/smudge.mdwn | 26 +------------- doc/todo/v7_path_toward_default.mdwn | 52 ++++++++++++++++++++++++++++ 2 files changed, 53 insertions(+), 25 deletions(-) create mode 100644 doc/todo/v7_path_toward_default.mdwn diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index 81d3b779d6..fd4f408a0f 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -1,30 +1,6 @@ git-annex should use smudge/clean filters. v7 mode -## warts - -* There are several bugs that are edge cases and - need more info or analysis. None of these seem like blockers - to keep v7 experimental or to replacing direct mode with v7. - - - - - - - - -### long term todos - -* Potentially: Use git's new `filter..process` interface, which will - let only 1 git-annex process be started by git when processing - multiple files, and so should be faster. - - See [[todo/Long_Running_Filter_Process]] .. it's not currently actually a - win but might be a good way to improve git to work better with v7. - -* Eventually (but not yet), make v7 the default for new repositories. - Note that the assistant forces repos into direct mode; that will need to - be changed then, and it should enable annex.thin instead. - -* Later still, remove support for direct mode, and enable automatic - v5 to v7 upgrades. +[[done]]! Continued in [[v7_path_toward_default]] ### historical notes diff --git a/doc/todo/v7_path_toward_default.mdwn b/doc/todo/v7_path_toward_default.mdwn new file mode 100644 index 0000000000..2e48b10aec --- /dev/null +++ b/doc/todo/v7_path_toward_default.mdwn @@ -0,0 +1,52 @@ +Tracking v7 progress toward becoming the default. + +## step 1: release + +done + +## step 2: default for new direct mode repositories + +Done when using the command line. 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 + +Direct mode is very buggy and limited, so it's easy for v7 (with adjusted +unlocked branches) to be better than it. + +Need to give it some time for problems to be found though. + +Here are some problems that need to be investigated first: + + - + - + - + +Also need to wait until git-annex v7 is widely supported. In Debian stable +seems reasonable. A direct mode repository may be used by multiple +machines, some not supporting v7 and some that do. + +## step 4: automatic v5 to v7 upgrades + +Since v5 repos and v7 repos not using unlocked files are functionally +almost identical, this is unlikely to break much. Unlocking files will of +course change behavior though. + +This needs to be deferred until every git-annex likely to be in use +supports v7. A v5 repository may be used by multiple +machines, some not supporting v7 and some that do. Probably around the same +time auto-upgrade from direct mode is done then. + +## step 5: default for all new repositories + +Could probably happen fairly soon after default in direct mode. + +## step 6: remove support for direct mode + +Will simplify a lot of code. + +## step 6: remove support for v5 + +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?