From 3553867b66fe0140007c905a7c655af1d0ba7898 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 7 Nov 2019 13:23:32 -0400 Subject: [PATCH] v7 to v8 auto-upgrade bump version to 8 and update NEWS about it --- Annex/Version.hs | 2 +- NEWS | 20 ++++++++++++++++++++ doc/todo/sqlite_database_improvements.mdwn | 2 ++ doc/upgrades.mdwn | 3 +++ git-annex.cabal | 2 +- 5 files changed, 27 insertions(+), 2 deletions(-) diff --git a/Annex/Version.hs b/Annex/Version.hs index 4a8e2f9840..ca987bf208 100644 --- a/Annex/Version.hs +++ b/Annex/Version.hs @@ -38,7 +38,7 @@ autoUpgradeableVersions = M.fromList , (RepoVersion 4, RepoVersion 5) , (RepoVersion 5, RepoVersion 6) , (RepoVersion 6, RepoVersion 7) - -- , (RepoVersion 7, RepoVersion 8) + , (RepoVersion 7, RepoVersion 8) ] versionField :: ConfigKey diff --git a/NEWS b/NEWS index df2f7612ba..a4df76fb0d 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,23 @@ +git-annex (8.20191107) upstream; urgency=medium + + This version of git-annex uses repository version 8 for all repositories. + + Existing repositories will be automatically upgraded by default. + You can prevent this, by runing: git config annex.autoupgraderepository false + + There is no user-visible change between v7 and v8. However, the upgrade + process involves regenerating some sqlite databases. There are a couple + consequences of the upgrade to keep in mind: + + * Any incremental fscks that were started in v7 won't resume where + they left off in v8, but will instead begin again from the first file. + * An interrupted export that was started in v7 won't resume where it left + off after upgrade to v8; files will be re-uploaded to the export remote. + * After the upgrade, git-annex will in some situations have to do extra + work while it finishes populating its sqlite databases. + + -- Joey Hess Thu, 07 Nov 2019 13:21:11 -0400 + git-annex (7.20191024) upstream; urgency=medium When annex.largefiles is not configured, `git add` and `git commit -a` diff --git a/doc/todo/sqlite_database_improvements.mdwn b/doc/todo/sqlite_database_improvements.mdwn index b0982b95f1..a843ca14c3 100644 --- a/doc/todo/sqlite_database_improvements.mdwn +++ b/doc/todo/sqlite_database_improvements.mdwn @@ -165,3 +165,5 @@ remaining todo: > Alternatively, can keep the old database code and use it to read the old > databases during the migration. But then bad data that got in due to the > encoding problems will persist. + +[[done]] --[[Joey]] diff --git a/doc/upgrades.mdwn b/doc/upgrades.mdwn index ccdd931a9f..78772257b0 100644 --- a/doc/upgrades.mdwn +++ b/doc/upgrades.mdwn @@ -59,6 +59,9 @@ re-populated. Any incremental fscks that were started in v7 won't resume where they left off in v8, but will instead begin again from the first file. +An interrupted export that was started in v7 won't resume where it left off +after upgrade to v8; files will be re-uploaded to the export remote. + After the upgrade, git-annex will in some situations have to do extra work while it finishes populating the new databases. After this one-time speed cost, git-annex's speed will improve when using the new and improved diff --git a/git-annex.cabal b/git-annex.cabal index cac61c94f7..89d3ab7b20 100644 --- a/git-annex.cabal +++ b/git-annex.cabal @@ -1,5 +1,5 @@ Name: git-annex -Version: 7.20191106 +Version: 8.20191107 Cabal-Version: >= 1.8 License: AGPL-3 Maintainer: Joey Hess