git-annex/doc/todo/v11_changes.mdwn

This is a todo for collecting changes that could lead to a v11 repository
version.

* Append to journal files even when annex.alwayscompact=true.
  This can make it a lot faster in some cases.
  See note in Annex.Branch.changeOrAppend.

  It's important that this only happen when no git-annex version
  older than 10.20220724 can plausibly be running in a repository
  after upgrading to the repo version that enables this. Depending on the
  timing of v11, this may need to be put in a v12 upgrade that is delayed
  some amount of time (eg 1 year) after v11.

* Finish the transition of git-annex sync defaulting to --content.
  A warning was added in May 2023 when it's run in a way that will change
  behavior. It would be good to wait until all git-annex users have
  gotten the version with the warning, and used it for a while,
  before finishing the transition. This does not need to be tied to a
  repository version change really, but it would be reasonable to do so.
prevent appends except when annex.alwayscompact=false I would like for a new repo version to enable appends, but to do so safely would need a v11 followed by a 1 year delay followed by a v12 that does it. Since a similar v9 and v10 transition is currently happening, and is less than 6 months along in most repos, it does not feel wise to stack up another year-long transition behind that. What if I need to hurry up a new repo version for some other change? Added todo so I remember to make this change at some time when a v11 and probably v12 repo version do make sense. Sponsored-by: Dartmouth College's DANDI project 2022-07-20 17:19:06 +00:00			`This is a todo for collecting changes that could lead to a v11 repository`
			`version.`

			`* Append to journal files even when annex.alwayscompact=true.`
			`This can make it a lot faster in some cases.`
			`See note in Annex.Branch.changeOrAppend.`

			`It's important that this only happen when no git-annex version`
			`older than 10.20220724 can plausibly be running in a repository`
			`after upgrading to the repo version that enables this. Depending on the`
			`timing of v11, this may need to be put in a v12 upgrade that is delayed`
			`some amount of time (eg 1 year) after v11.`
sync: Started transition to --content being enabled by default When used without --content or --no-content, warn about the upcoming transition, and suggest using one of the options, or setting annex.synccontent. Sponsored-by: Brett Eisenberg on Patreon 2023-05-17 17:23:42 +00:00
			`* Finish the transition of git-annex sync defaulting to --content.`
			`A warning was added in May 2023 when it's run in a way that will change`
			`behavior. It would be good to wait until all git-annex users have`
			`gotten the version with the warning, and used it for a while,`
			`before finishing the transition. This does not need to be tied to a`
			`repository version change really, but it would be reasonable to do so.`