No tags for since 26.0.1.13 (May 27)

[Orgad Shaneh]

Hi,

I see there are several "Release new version X" commits, but there are no tags for them.

Is this intended?

[Richard Fuchs]

Which ones do you mean exactly? The one for 26.2 in the master branch?

[Orgad Shaneh]

commit 531237706919c2be443ec33d84994386b8fb1dac (origin/master, origin/HEAD)
Author: Sipwise Jenkins Builder <jen...@sipwise.com>
Date:   Mon Jun 15 15:34:23 2026 +0200

    Release new version 26.2.0.0+0~mr26.2.0.0

commit 040b8c768abcd07fc1094b283c70673ff2a03c64 (HEAD -> mr26.1, origin/mr26.1)
Author: Sipwise Jenkins Builder <jen...@sipwise.com>
Date:   Mon Jun 15 15:33:56 2026 +0200

    Release new version 26.1.1.0+0~mr26.1.1.0

[Richard Fuchs]

Those are just commits to create new branches (update the version in the changelog), specifically to prepare for future releases. Actual tagged releases have a non-zero release (last) number. The actual first tagged release for 26.1 will be 26.1.1.1.

Cheers

--
You received this message because you are subscribed to the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtpengine+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rtpengine/3c99dca5-ccde-4b27-a125-48cd1f24c27bn%40googlegroups.com.

[Orgad Shaneh]

I see. Thank you and sorry for the noise.