[wishlist][doc] prefix "time to upgrade" with "supported since v1.2.3" in the doc :-) #586

New Issue

Closed

opened 2022-09-13 08:28:27 +00:00 by grin · 1 comment

grin commented 2022-09-13 08:28:27 +00:00

Copy Link

What I'm trying to do and why

Reading the docs, to prevent asking stupid questions! :-)

Okay, but I see you're curious

...I wanted to rename an archive to prevent it to be pruned (aka. "protect" or "keep").

What I wish

borgmatic borg WhatEver seems to be a new feature, and the documentation nicely hints that.

Except it would be really useful to mark that when a feature became supported, instead of letting the poor sod browse the revision history or the tags to figure out what version was the first supporting the feature. (Especially interesting when someone, like your truly, uses a distro-provided version and cannot just make it upgrade to trunk.)

Environment

documentation version: current

borgmatic version: Debian/stable, which may or may not be behind.

#### What I'm trying to do and why Reading the docs, to prevent asking stupid questions! :-) ##### Okay, but I see you're curious ...I wanted to rename an archive to prevent it to be pruned (aka. "protect" or "keep"). #### What I wish `borgmatic borg WhatEver` seems to be a new feature, and the documentation nicely hints that. Except it would be really useful to mark that *when* a feature became supported, instead of letting the poor sod browse the revision history or the tags to figure out what version was the first supporting the feature. (Especially interesting when someone, like your truly, uses a distro-provided version and cannot just make it upgrade to trunk.) #### Environment **documentation version:** current **borgmatic version:** Debian/stable, which may or may not be behind.

witten referenced this issue from a commit 2022-09-13 16:05:45 +00:00

Note version of borgmatic needed for "borgmatic borg" action (#586).

witten commented 2022-09-13 16:06:28 +00:00

Owner

Copy Link

Except it would be really useful to mark that when a feature became supported, instead of letting the poor sod browse the revision history or the tags to figure out what version was the first supporting the feature. (Especially interesting when someone, like your truly, uses a distro-provided version and cannot just make it upgrade to trunk.)

I'd started doing this in the documentation when implementing newer features, but I haven't gone back and added "new in version x.y.z" retroactively. As part of this ticket, I'll note the version required for the "borgmatic borg" feature. If there are any other features you're wondering about, just let me know and I'll add the version for those as well! Thanks for filing this.

borgmatic version: Debian/stable, which may or may not be behind.

It most definitely is. :) In fact, I'd go so far as to say that version is unsupported. On Debian stable, which I use myself in a few places, I recommend installing borgmatic by via pip or another mechanism. I realize this is a hassle, but IMO this is part of the cost of running such a stable, infrequently updated Linux distro.

> Except it would be really useful to mark that when a feature became supported, instead of letting the poor sod browse the revision history or the tags to figure out what version was the first supporting the feature. (Especially interesting when someone, like your truly, uses a distro-provided version and cannot just make it upgrade to trunk.) I'd started doing this in the documentation when implementing newer features, but I haven't gone back and added "new in version x.y.z" retroactively. As part of this ticket, I'll note the version required for the "borgmatic borg" feature. If there are any other features you're wondering about, just let me know and I'll add the version for those as well! Thanks for filing this. > borgmatic version: Debian/stable, which may or may not be behind. It most definitely is. :) In fact, I'd go so far as to say that version is unsupported. On Debian stable, which I use myself in a few places, I recommend installing borgmatic by [via pip](https://torsion.org/borgmatic/docs/how-to/set-up-backups/#installation) or [another mechanism](https://torsion.org/borgmatic/docs/how-to/set-up-backups/#other-ways-to-install). I realize this is a hassle, but IMO this is part of the cost of running such a stable, infrequently updated Linux distro.

witten closed this issue 2022-09-13 16:06:28 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#586

No description provided.