[Pkg-giraffe-discuss] Kopano Webapp plugins versioning
Jan Engelhardt
jengelh at inai.de
Sat Sep 28 09:43:12 BST 2019
On Tuesday 2019-09-24 08:18, Roel van Meer wrote:
> Jan Engelhardt writes:
>
>> > Sorry, I don't follow. Yes, it means that it is possible to determine the
>> > commit that was used for 2.0.0.23, but it doesn't mean I can see in the Git
>> > repo which commit was used for the latest release. Or am I missing
>> something
>> > here?
>>
>> ยป tag="v2.0.0"; for i in $(git rev-list --reverse --first-parent
>> "$tag..origin/master"); do ofs="$(git rev-list --count "$tag..$i")"; echo
>> "$tag+git$ofs => $i"; done
>>
>> v2.0.0+git2 => e4e99de315cd19752992b3451b51d7fea7d437df
>> v2.0.0+git4 => 6fc709fae42873ad3ad2a530231049e2a835fe40
>> ...
>
> Yes, this relation is clear, but it doesn't tell me which commit is tested,
> approved and released as the latest stable version.
That is not some kind of information that git repositories necessarily
carry (anywhere).
In KC for example, the approved production set is not just one commit,
but a branch and all its commits (preferably the most recent commit of
said branch).
Then there is KW which seem to have just one flowing branch (master),
where you can expect that the approved production set is either "any
time" or at tags.
More information about the Pkg-giraffe-discuss
mailing list