5 Apr
2016
5 Apr
'16
2:03 p.m.
I noticed that 15 days ago there was rtpengine commit
https://github.com/sipwise/rtpengine/commit/aac8899b612dc8103b89f3f9c921f88…
titled "Release new version 4.4.0.0+0~mr4.4.0.0", but I could not find
the corresponding branch or tag.
If someone wants to use that version, is 'git archive
aac8899b612dc8103b89f3f9c921f88af3501303' the only way to do so?
-- Juha
5 Apr
5 Apr
3:26 p.m.
On 05/04/16 08:03 AM, Juha Heinanen wrote:
I noticed that 15 days ago there was rtpengine commit
https://github.com/sipwise/rtpengine/commit/aac8899b612dc8103b89f3f9c921f88…
titled "Release new version 4.4.0.0+0~mr4.4.0.0", but I could not find
the corresponding branch or tag.
If someone wants to use that version, is 'git archive
aac8899b612dc8103b89f3f9c921f88af3501303' the only way to do so?
The version tag in the master branch is always one ahead of the latest
release branch, to make sure that builds from master are seen as newer
than release branches. The last release branch is 4.3.x, so master was
updated to 4.4. It's not a real released version until 4.4.1 is branched.
Cheers
4:56 p.m.
Richard Fuchs writes:
The version tag in the master branch is always one
ahead of the latest
release branch, to make sure that builds from master are seen as newer
than release branches. The last release branch is 4.3.x, so master was
updated to 4.4. It's not a real released version until 4.4.1 is
branched.
OK, thanks for the explanation.
-- Juha
2968
days inactive
2968
days old
2 comments
2 participants
participants (2)
-
Juha Heinanen -
Richard Fuchs