diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-07-06 14:54:50 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-07-06 14:54:50 -0400 |
| commit | 10e7caafe179c210eaae2b9a91297f48ae9b75b3 (patch) | |
| tree | 745af1d217802b962eb4901cb8ff98e37efcbb3d | |
| parent | 49d092fd92ea14ac44ba8f1906978fcead4f5b4f (diff) | |
response
| -rw-r--r-- | doc/forum/v5_to_v6_upgrade_strategy/comment_3_46fb3f5b0a7fa13b6f16ccb9832dac7e._comment | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/v5_to_v6_upgrade_strategy/comment_3_46fb3f5b0a7fa13b6f16ccb9832dac7e._comment b/doc/forum/v5_to_v6_upgrade_strategy/comment_3_46fb3f5b0a7fa13b6f16ccb9832dac7e._comment new file mode 100644 index 000000000..189b50aef --- /dev/null +++ b/doc/forum/v5_to_v6_upgrade_strategy/comment_3_46fb3f5b0a7fa13b6f16ccb9832dac7e._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-07-06T18:50:34Z" + content=""" +I'd encourage you to not upgrade any production repositories to v6 yet. +It's still in beta state and has known problems. Currently all known +problems are only innefficiencies, but there could also still be bugs. + +When you do upgrade, you can upgrade your distibuted set of repos +peicemeal. v5 and v6 fully interoperate, until you start unlocking files in +the v6 clones of the repo. Once those unlocks get committed, the v5 clones +of the repo won't be able to access the unlocked file contents, and you'll +need to upgrade the clones then. + +At some point in the future, I expect v6 mode to be done and then git-annex +will automatically upgrade for you. So the easist approach is to just wait +for that. + +(Not addressing your problems with annex.thin here as you filed a separate +forum post and bug report about that.) +"""]] |