@eyedeekay
&zzz
+Irc2PGuest80463
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest10420
Irc2PGuest27560
Irc2PGuest32123
Irc2PGuest61213
Irc2PGuest64434
Irc2PGuest71617
Onn4l7h
Over
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh
ardu
b3t4f4c3___
b4dab00m
bak83
cumlord
dr4wd3
duanin2
duck
eyedeekay_bnc
kaffi
makoto
nilbog
ohThuku1
poriori_
pory
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
wew
x74a6
zzz
good monrning eyedeekay, two weeks in, assume you're done?
zzz
we gotta get these PRs fixed and moving. Is gitea going to be usable for PRs at all?
zzz
my guess is we're targeting an early-december release?
eyedeekay
Yeah early december, gitea will be usable for PR's but I am going to have to recreate 519 again
eyedeekay
I have a scheduling forum post to make today, several emails to send, and the reviews to finish today
eyedeekay
Also going to push a draft of the go-i2p blog post
zzz
ok good. 519 is just a little one.
zzz
I need to finish jetty12 and the tunnel throttler PRs
zzz
then get started on PQ transports for testing that I keep promising orignal
zzz
android is done? I saw 2.10.1 appear on my phone
eyedeekay
Yes it is, all pages fixed
eyedeekay
I am going to do the Java 11 migration this week, you were right 17 is not an option but 11 gets me everything important I want for it anyway
zzz
reporter of the netdb page problem I think also complained the android release wasn't on the website, did you fix that?
eyedeekay
Look like it is there now
eyedeekay
*looks
zzz
HEAD on www is from the 17th and I know you did 2.10.1 after that so I don't think it could be up to date
zzz
re: java 11, we said we'd discuss it after the release so let's do it
zzz
tell us what the min android version is you're proposing, and why, and what % of the user base we will strand, and is that acceptable
eyedeekay
Android 11 was the first to support Java 11, that would be the lowest release that could use 11, however I can target compatibility with Java 8 which means I do not think I would have to abandon any
eyedeekay
My main motivation for wanting to migrate up is to be able to the up-to-date version of the Android Gradle Plugin, which will significantly simplify building it
zzz
if you're requiring android 11, then you're abandoning phones <= 10 by definition, no?
eyedeekay
I am not quite sure but I do not think so, there are these compatibility flags in the gradle files that let you target different Java versions than the one you are using yourself, called SOURCE_COMPATIBILITY and TARGET_COMPATIBILITY, along with these 'desugaring' features that replace new features with code that does not require them
zzz
yeah but the compat lib is different
eyedeekay
I won't know for sure until I actually build with Java 11 and load it on an Android 9 though
zzz
but what unlocks your desired version of the gradle plugin? JAVA 11 or ANDROID 11?
eyedeekay
Java 11 specifically
zzz
ok but java 11, at least the source stuff, isn't supported until android 11
zzz
maybe binary?
zzz
our current minimum is android 5, right?
eyedeekay
In theory yeah
eyedeekay
I don't actually have any 5 installs in play store or anything
zzz
so why is that if there's compatibility flags
zzz
we need answers to this stuff via research, not testing. we need to know what we're doing
zzz
I think android 11 min is probably the right choice, and the first to support java 11
zzz
but it has to be that making that the minimum and dropping <= 10 simplifies things somehow
zzz
but what % is <= 10
eyedeekay
10 is actually the lowest I see in the play store right now and there are less than 50, so like 1%
zzz
that's specifically for our app?
eyedeekay
Yes and they fuzz the numbers so we don't know the exact but I know enough to see less than 50
zzz
this chart is about 10% composables.com/android-distribution-chart
zzz
oops no 20%
eyedeekay
that could be on account of the play device certification or something, google hiding the old versions, or people disabling telemetry somehow
zzz
google doesnt publish official numbers any more
eyedeekay
Obviously we don't get stats from f-droid or anything
zzz
an android 11 requirement would lose all but one of my devices but they're pretty old
zzz
did you see the complaint that there's no PQ i2ptunnel option?
eyedeekay
On Android? No but I did see the shared tunnel thing where it was greyed out
zzz
yeah may have been in saltr
zzz
ofc we have it labeled as beta for now so no big deal but assuming we relabel it for next release you'll need to put it in the UI
zzz
anyway my presumption of a android 11 reqmt is we strand somewhere between 1% and 20% of our user base so please research if that's true
eyedeekay
Ack will go through the scrollback to get the details on the PQ thing
eyedeekay
I will figure out the who do we strand question, starting with figuring out what these flags I'm seeing will and will not do
zzz
I don't think we need to open the floodgates and start allowing java 11 idioms in core/router/streaming/i2ptunnel immediately
zzz
for one thing we need to coordinate with bigly
zzz
not sure if he can handle it
zzz
I did ask once but can't remember the answer
eyedeekay
Ack. My goal will be to cause as little disruption as possible.
eyedeekay
I'll get definitive answers on those target/compatibility flags
zzz
also need to decide 2.11 or 3.0
eyedeekay
I'll make that question part of the scheduling post
zzz
who are you asking that question? It's up to us to decide
eyedeekay
Us, just on the forum thread
eyedeekay
My vote would go to 2.11 at the moment
zzz
I'm Swiss atm