(03:01:40 PM) eyedeekay: Hi everyone, welcome to the dev meeting
(03:01:40 PM) eyedeekay: 1. Hi 
(03:01:40 PM) eyedeekay: 2. Release Status (1.7.0 / 0.9.53)
(03:02:10 PM) zlatinb: hi
(03:02:12 PM) zzz: hello
(03:02:39 PM) eyedeekay: Anything else to add to the agenda today before we start the release status?
(03:03:01 PM) zlatinb: I have two small items that could fall into a "wishlist for 1.8.0" item
(03:03:25 PM) eyedeekay: 3) 1.8.0 wishlist
(03:04:24 PM) eyedeekay: 2. Release Status(1.7.0/0.9.53)
(03:05:37 PM) eyedeekay: On my end I do have one remaining item, there is an issue with the .aab bundle build process where static resources that are included from the `i2p.i2p` build are deleted and from the final .aab
(03:06:06 PM) eyedeekay: For the time being, GPlay is delayed, I'm working on it today and should be done soon.
(03:07:53 PM) eyedeekay: F-Droid and Freestanding are both .apk's that use the old build process that isn't broken, so it still works.
(03:07:53 PM) eyedeekay: Are there any other outstanding release processes to finish?
(03:10:03 PM) eyedeekay: zzz anything to add to the release status topic from your end? I understand BiglyBT released their plugin today, is that correct?
(03:10:22 PM) zzz: yes
(03:10:48 PM) zzz: based on expl. build success stats, we've rapidly recovered from i2pd's regression in the last release
(03:10:52 PM) zzz: http://stats.i2p/docs/buildsuccess.png
(03:11:11 PM) zzz: and are now at a higher point than any time in the last few years iirc
(03:12:11 PM) zzz: things should settle out in another week and we'll see where we are
(03:12:13 PM) zzz: eot
(03:12:21 PM) eyedeekay: That's really excellent news. Glad things are looking good so far.
(03:12:32 PM) eyedeekay: Thanks zzz
(03:12:50 PM) eyedeekay: 3. 1.8.0 wishlist
(03:13:17 PM) eyedeekay: zlatinb take it away
(03:13:44 PM) zlatinb: hi, 1) is speeding up initial exploratory build time and 2) JNA
(03:14:05 PM) zlatinb: 1: I've been doing some analysis, 75% of the exploratory tunnels that do build do so in less than 500ms
(03:14:29 PM) zlatinb: out of ~30 samples the slowest successful build was less than 2500ms
(03:14:46 PM) zlatinb: whereas the timeout we have now is 13000 ms, I think reducing that will get the router to RUNNING state faster
(03:15:07 PM) zlatinb: we don't have to decide now, just floating the idea out there
(03:15:12 PM) zlatinb: eot on 1
(03:15:33 PM) zzz: no objections on 1
(03:15:56 PM) eyedeekay: Sounds like an interesting experiment to try at least, it doesn't seem like it could do any harm
(03:16:12 PM) eyedeekay: If all the successful builds are so short
(03:16:13 PM) zlatinb: 2: JNA - we'll definitely need to add JNA to the windows easy install bundle in order to elevate priviledge during auto-update.  ProcessBuilder fails if the process requires elevation.
(03:16:20 PM) zzz: although I'd like to see data over a longer time period before we pick the new number
(03:16:25 PM) zlatinb: sure
(03:16:42 PM) zzz: please back up and define JNA
(03:16:43 PM) zlatinb: (back to 1) I'll leave a router running with logging enabled
(03:17:12 PM) zlatinb: (back to 2): JNA is Java Native A-something but it's basically a Java wrapper of native windows linux and mac libraries
(03:17:27 PM) zlatinb: so instead of writing native code you write java code
(03:17:52 PM) zlatinb: two jars combined size 3MB, compressed with LZMA down to 2MB
(03:18:11 PM) HTTP/1.1 200 OK
Cache-Control: public, max-age=21600, no-transform
Content-Disposition: inline; filename="309.log"; filename*=UTF-8''309.log
Last-Modified: Tue, 01 Mar 2022 20:40:38 GMT
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Length: 7494
Date: Wed, 23 Jul 2025 11:06:25 GMT
Access-Control-Expose-Headers: Content-Disposition
Content-Type: text/plain; charset=utf-8
Set-Cookie: i_like_gitea=1a1cd9772e03c2c2; Path=/; HttpOnly; Secure; SameSite=Lax
Set-Cookie: _csrf=bMQWacMQYBm9bPMRQ8cs2VYOXdA6MTc1MzI2ODc4NTY4MjQ1ODAwNw; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax
Etag: "df8705a5c42d51c648d9a6486600a878f9b49c20"
Connection: close
X-Cache-Status: HIT
X-Cache-Age: 0

(03:01:40 PM) eyedeekay: Hi everyone, welcome to the dev meeting
(03:01:40 PM) eyedeekay: 1. Hi 
(03:01:40 PM) eyedeekay: 2. Release Status (1.7.0 / 0.9.53)
(03:02:10 PM) zlatinb: hi
(03:02:12 PM) zzz: hello
(03:02:39 PM) eyedeekay: Anything else to add to the agenda today before we start the release status?
(03:03:01 PM) zlatinb: I have two small items that could fall into a "wishlist for 1.8.0" item
(03:03:25 PM) eyedeekay: 3) 1.8.0 wishlist
(03:04:24 PM) eyedeekay: 2. Release Status(1.7.0/0.9.53)
(03:05:37 PM) eyedeekay: On my end I do have one remaining item, there is an issue with the .aab bundle build process where static resources that are included from the `i2p.i2p` build are deleted and from the final .aab
(03:06:06 PM) eyedeekay: For the time being, GPlay is delayed, I'm working on it today and should be done soon.
(03:07:53 PM) eyedeekay: F-Droid and Freestanding are both .apk's that use the old build process that isn't broken, so it still works.
(03:07:53 PM) eyedeekay: Are there any other outstanding release processes to finish?
(03:10:03 PM) eyedeekay: zzz anything to add to the release status topic from your end? I understand BiglyBT released their plugin today, is that correct?
(03:10:22 PM) zzz: yes
(03:10:48 PM) zzz: based on expl. build success stats, we've rapidly recovered from i2pd's regression in the last release
(03:10:52 PM) zzz: http://stats.i2p/docs/buildsuccess.png
(03:11:11 PM) zzz: and are now at a higher point than any time in the last few years iirc
(03:12:11 PM) zzz: things should settle out in another week and we'll see where we are
(03:12:13 PM) zzz: eot
(03:12:21 PM) eyedeekay: That's really excellent news. Glad things are looking good so far.
(03:12:32 PM) eyedeekay: Thanks zzz
(03:12:50 PM) eyedeekay: 3. 1.8.0 wishlist
(03:13:17 PM) eyedeekay: zlatinb take it away
(03:13:44 PM) zlatinb: hi, 1) is speeding up initial exploratory build time and 2) JNA
(03:14:05 PM) zlatinb: 1: I've been doing some analysis, 75% of the exploratory tunnels that do build do so in less than 500ms
(03:14:29 PM) zlatinb: out of ~30 samples the slowest successful build was less than 2500ms
(03:14:46 PM) zlatinb: whereas the timeout we have now is 13000 ms, I think reducing that will get the router to RUNNING state faster
(03:15:07 PM) zlatinb: we don't have to decide now, just floating the idea out there
(03:15:12 PM) zlatinb: eot on 1
(03:15:33 PM) zzz: no objections on 1
(03:15:56 PM) eyedeekay: Sounds like an interesting experiment to try at least, it doesn't seem like it could do any harm
(03:16:12 PM) eyedeekay: If all the successful builds are so short
(03:16:13 PM) zlatinb: 2: JNA - we'll definitely need to add JNA to the windows easy install bundle in order to elevate priviledge during auto-update.  ProcessBuilder fails if the process requires elevation.
(03:16:20 PM) zzz: although I'd like to see data over a longer time period before we pick the new number
(03:16:25 PM) zlatinb: sure
(03:16:42 PM) zzz: please back up and define JNA
(03:16:43 PM) zlatinb: (back to 1) I'll leave a router running with logging enabled
(03:17:12 PM) zlatinb: (back to 2): JNA is Java Native A-something but it's basically a Java wrapper of native windows linux and mac libraries
(03:17:27 PM) zlatinb: so instead of writing native code you write java code
(03:17:52 PM) zlatinb: two jars combined size 3MB,