diff options
| author |  mhauru <mhauru@web> | 2017-02-19 18:48:59 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-02-19 18:48:59 +0000 |
| commit | a66f37e9d62e8479446237a3baaf737db726f7c5 (patch) | |
| tree | e2cc09926d924de487ad64682fe7af64ee881a9b | |
| parent | daccbf5ab2c5755d6eb9a38f50b4b8f703beef82 (diff) | |
| -rw-r--r-- | doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__.mdwn b/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__.mdwn new file mode 100644 index 000000000..2c70e371a --- /dev/null +++ b/doc/forum/Joey__44___when_would_you_guess_v6_to_be_ready__63__.mdwn @@ -0,0 +1,3 @@ +A question for Joey: What's the expected schedule for v6 repos becoming solid enough to make them the default? Is it next on the priority list or are you still waiting for some git patches to propagate through or something like that? + +I'm asking because I make extensive use of v5 direct mode repos. They sometimes give me a bit of trouble in ways which I hope indirect, unlocked, thin v6 repos could fix. However, I don't want to switch to v6 as long as Joey considers it too experimental/unfinished to be made the default repo format. So I'm trying to decide whether I should put in the effort to investigate the issues I'm having (which are annoying but not catastrophic), or just wait until v6 is ready for prime time. |