Does libr3-0 in unbuntu 18.04 the latest version?

[xiangnanscu]

root@win10:~/r3# apt-cache show libr3-0
Package: libr3-0
Architecture: amd64
Version: 1.3.4-1
Multi-Arch: same
Priority: optional
Section: universe/libs
Source: libr3
Origin: Ubuntu
Maintainer: Ubuntu Developers <[email protected]>
Original-Maintainer: ChangZhuo Chen (陳昌倬) <[email protected]>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 49
Provides: libr3
Depends: libc6 (>= 2.14), libpcre3
Filename: pool/universe/libr/libr3/libr3-0_1.3.4-1_amd64.deb
Size: 18314
MD5sum: b72fd1516291726f41518b58de42956f
SHA1: 4da37470035a52fc6f655f4ca4c49ae5cdc556f8
SHA256: 80ad8e4bedd270d48f716c025c112db345bc3ccaba840c0f6f57b1d2c404d9a6
Homepage: https://github.com/c9s/r3
Description-en: High-performance URL router library
 R3 is an URL router library with high performance, thus, it's implemented in
 C.  It compiles your route paths into a prefix trie. By using the constructed
 prefix trie in the start-up time, you can dispatch routes with efficiency.
Description-md5: bff9cd009e92f90d21c79f0e6537cea1

[c9s]

I guess no, need to ping @czchen to ship a new release?

[czchen]

Does it any tag point to new release? The latest tag in https://github.com/c9s/r3/tags is still 1.3.4.

[c9s]

I think we're working on 2.0, @bjosv what do you think?

[bjosv]

Yes, a new tag would be nice. There are many changes in the 2.0 branch that would be nice to get in an official release.
Should we try to include the pcre2 lift in 2.0 as well? I will run a benchmark of the change first so we have those numbers.

I've also seen that we have an older milestone-list for a 2.0 release that maybe should be handled, not sure.
I have not looked through them yet, but can take a quick look.

[c9s]

Sure! let’s include PCRE2 in 2.0 ? that would be great! Björn Svensson ***@***.***>於 2023年10月16日 週一，22:03寫道：

…

Yes, a new tag would be nice. There are many changes in the 2.0 branch that would be nice to get in an official release. Should we try to include the pcre2 lift in 2.0 as well? I will run a benchmark of the change first so we have those numbers. I've also seen that we have an older milestone <https://github.com/c9s/r3/milestone/1>-list for a 2.0 release that maybe should be handled, not sure. I have not looked through them yet, but can take a quick look. — Reply to this email directly, view it on GitHub <#139 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMNTTG3LCO7DNEJQRE6ZLX7U5ETAVCNFSM46WLZNNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGQ2TKNBZGE2A> . You are receiving this because you commented.Message ID: ***@***.***>