mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

close

Browse source
This commit is contained in:
Joey Hess 2021-08-09 12:31:36 -04:00
parent 15ef5e62d2
commit c9b1b7d067
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/downloads.kitenet.net_do_not_correspond_in_version.mdwn
View file

@ -41,3 +41,5 @@ $> git tag | grep 202108
``` ```
so it seems odd so it seems odd
> [[notabug|done]] --[[Joey]]

21
doc/bugs/downloads.kitenet.net_do_not_correspond_in_version/comment_1_337c17e686723aee193e898fd7ee3558._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2021-08-09T16:11:54Z"
content="""
6e67ea5d7 is 2 commits away from the tag for 8.20210803.
The two commits are whitespace changes and the commit that increased the
version number.
I can either push the release to git and bless the builds current at the
same time, or wait some amount of time after the release tag for the builds
to catch up. That could be some arbitrary amount of time, because builds
fail for various reasons outside my control, or are slow.
It would also need a separate build process than the autobuilds of master,
to build against release tags. Which adds even more ways for things to go
wrong or be delayed.
Therefore, I have chosen this compromise. It is not new, and if you
consider it a bug, well, you can build against the release tag if you wish.
"""]]