@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+acetone
+altonen
+dr|z3d
+hagen
+hk
+lbt
+mareki2p
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest12735
Irc2PGuest28644
Irc2PGuest4450
Irc2PGuest59134
Irc2PGuest87589
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
aeiou
ardu
b3t4f4c3__
cumlord
dr4wd3_
eyedeekay_bnc
not_bob_afk
onon_
plap
poriori_
profetik1
qend-irc2p
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
orignal
fixed the first problem
zzz
review deadline in one hour
orignal
problem 2 is not started yet
zzz
starting the build, files in an hour
zzz
torrent is up, newsxml metadata checked in, draft blog post is up
orignal
another release?
zzz
yeah fixing a screwup
orignal
are you going to include ML-KEM into the next major release?
zzz
no
zzz
git tagged and pushed, checksums added to blog post
zzz
updater files are smaller than usual because I omitted geoip
zzz
starting launchpad build, s390x queue is 9 hours, so unlikely to have them all done today
zzz
ha, they're all low-priority, our s390x is building now. This might go pretty quick
eyedeekay
Not firm yet, looking at mid-to-late June
orignal
it's too early to talk about June
zzz
I'd vote for about a month earlier; that's a looong way from our last major release Feb. 4
zzz
might be driven by i2pd's requirements, not ours, since they haven't done any point releases
eyedeekay
mid-late may then? Could also work for me, I am pretty flexible. Happy to defer to orignal's scheduling needs on this, I plan to be deep in go-i2p for a while after today
zzz
the reason to start making a plan is I don't want to merge a ton of MRs and then have i2pd want a release in two weeks
orignal
fine for me
eyedeekay
If mid-to-late may is fine for orignal it's fine for me and gives us time to get MR's in a timely manner then I think that makes it mid-to-late May
zzz
eyedeekay, here's my up-to-date 2.9.0 roadmap, with items waiting on your review in orange: stats.i2p/docs/roadmap-2.9-zzz.html
eyedeekay
Let's plan for the week of the 19th for the tag freeze, review period, with release at the end of that week
eyedeekay
Ack zzz I'll go after those MR's in the next few days, probably starting with 240
eyedeekay
(was already having a look at that one)
zzz
if tag freeze is week of 19th then release would be the end of the week after, May 2
zzz
gotta give the translators about 10 days
eyedeekay
I was referring to May 19th which would make the end it May 30th but yeah, same timeline moved a month later
eyedeekay
I can't do late April unfortunately I'll be on the road
zzz
sorry I meant June 2
eyedeekay
As long as we all understand the timeline, at least ten days from tag freeze
eyedeekay
Review the last week before release
zzz
memorial day weekend is may 24-26, perhaps better to avoid a release then, so June 2 sounds right
eyedeekay
Good. June 2 it is
zzz
wow believe it or not, all 3 launchpad builds are done. Still have to do the copying, but I'm gonna be done today
eyedeekay
Wow nice
eyedeekay
Mirror's updated so I'll just build the newsfeeds
zzz
maybe we should always do releases on the weekend...
zzz
eyedeekay, for 2.8.1 in newsxml I saw you checked in a few translations, but not all
zzz
you are pulling all translations even if you don't check them in, right?
zzz
because you have to get the metadata even if they don't translate everything
zzz
I haven't done any tests to see if all languages have the latest, but can you assure that they do?
eyedeekay
Yeah tx pull gets them all but if they're not tracked in git they didn't make it to the git repo, I'll make sure I check them all into git
zzz
ok your last checkin was only 7 translations, and we have 35 tracked in git
zzz
so something doesn't add up
zzz
no particular need to keep them checked in every time, but either do them all or don't
eyedeekay
Hm, I'll figure it out, the command I've been using with tx is the one from the readme: `tx pull --use-git-timestamps -a` I'll see what I can find out
zzz
just worth a double-check that they all have the correct metadata
zzz
certainly don't want a situation where a bunch of countries don't get their updates
eyedeekay
Understood, I'll make sure it's right
zzz
correction, the metadata is in a separate file
zzz
so they would get the update, they just wouldn't have the latest console news
zzz
it should be pulling all 35 translations every time
dr|z3d
prettified roadmap: zzzmirror.i2p/roadmap_2.9.html
orignal
zzz, the spec doesn't mention DateTime
orignal
Send a data packet containing a Path Challenge block, an Address block (containing the new IP/port), and, typically, an ACK block, to the new IP and port.
orignal
basically my question is about order
orignal
or blocks
zzz
under 'Message Contents'
zzz
Message Contents
zzz
The Data messages should contain the following blocks. Order is not specified except that Padding must be last:
zzz
Path Challenge or Path Response block. Path Challenge contains opaque data, recommended 8 bytes minimum. Path Response contains the data from the Path Challenge.
zzz
Address block containing the recipient's apparent IP
zzz
DateTime block
zzz
ACK block
zzz
Padding block
orignal
yes I see but in which order?
zzz
Order is not specified except that Padding must be last
orignal
Datatime, address, path challenge, padding?
zzz
I'll be done with launchpad and debian in 45 minutes... eyedeekay how's the news going?
zzz
debian and launchpad done
eyedeekay
All built just checking it over and getting it onto the news servers
zzz
great
eyedeekay
Messed them up, won't take long to rebuild, will be there before 5
eyedeekay
Ok that should be the main newsfeed updated and all the translations available to me checked in
zzz
I have a couple torrent leeches but not exactly a full popoff yet
zzz
I just double-checked the infohash is right
zzz
please double check things on your side on both hosts
zzz
seems a lot slower than normal
eyedeekay
Second feed isn't updated yet will be shortly
eyedeekay
there's the second feed updated
eyedeekay
rsync was just hanging on news_zh_TW.su3
zzz
still feels like you have the backup host right but not the primaryh
zzz
only 13 leeches reported by postman, should be a couple hundred
zzz
just did the CLI test, both look good
zzz
maybe I'm just misremembering what is typical
zzz
the download is so fast, leeches don't stay leeches for long
eyedeekay
I do sort of remember it being faster, but maybe there was a little more latency between when I did the news and when I announced I did the news when it was mostly me on the release
zzz
maybe it didn't 'pop' because you did the backup first
zzz
it seems fine. maybe the sha256 issue is slowing things down, dunno. we can check back in a couple days and see how it looks
zzz
I'll get going on 2.9.0 next week. Good luck on android and the bundle. You're doing the website, right?