Skip to content

Tags: yingyun001/vdsm

Tags

v4.18.9

Toggle v4.18.9's commit message
Vdsm 4.18.9 for oVirt 4.0.2

v4.18.8

Toggle v4.18.8's commit message
Vdsm 4.18.8 for oVirt 4.0.2

v4.18.7

Toggle v4.18.7's commit message
Vdsm 4.18.7 for oVirt 4.0.2

v4.18.6

Toggle v4.18.6's commit message
Vdsm 4.18.6

v4.17.33

Toggle v4.17.33's commit message
Vdsm 4.17.33 for the release 3.6.8

v4.16.38

Toggle v4.16.38's commit message
Vdsm 4.16.38

v4.18.5.1

Toggle v4.18.5.1's commit message
alias tag for 4.18.5

The problem was tag 4.18.5 was made against a wrong tree,
but this was detected only after the build.
So we add this tag against a the right tree.

v4.18.5

Toggle v4.18.5's commit message
Vdsm 4.18.5 for oVirt 4.0.1 RC1

v4.18.4.1

Toggle v4.18.4.1's commit message
Vdsm 4.18.4.1 for oVirt 4.0.0 GA

Rationale for this exceptional tagging is:

To unblock the 4.0.0 release process, the Vdsm 4.18.4.1 package was rebuild using renamed 4.18.3 source.
In order to keep git tagging consistent, we need to add the v4.18.4.1 tag on git hash 98fb604 corresponding
to v4.18.3 tag.
This will allow to yum update reverting to previous code without branching, bumping versions and so on.

v4.18.4

Toggle v4.18.4's commit message
Vdsm 4.18.4 for oVirt 4.0.0 RC