@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+RN_
+dr|z3d
+hk
+orignal
+postman
+wodencafe
Arch
DeltaOreo
FreeRider
FreefallHeavens
Irc2PGuest10850
Irc2PGuest19353
Irc2PGuest23854
Irc2PGuest46029
Irc2PGuest48064
Irc2PGuest77854
Nausicaa
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
Soni
T3s|4__
Teeed
aargh3
acetone_
anon4
b3t4f4c3
bak83_
boonst
cumlord
dr4wd3_
eyedeekay_bnc
hagen_
khb
mittwerk
plap
poriori
profetikla
rapidash
shiver_
solidx66
u5657_1
uop23ip
w8rabbit
weko_
x74a6
eyedeekay
focal builds just finished, will get those copied over
eyedeekay
Debians should be out at last
zzz
is that it? android?
zzz
did you add a line to the deb home page or shall I?
zzz
also pls checkin the debian changelogs
zzz
also see comments on your gitlab issue
eyedeekay
I will do the homepages, Android and Maven went out day-one so that should cover the lot
eyedeekay
Pushed debian changelogs, pushed probable fix for i2ptunnel onto master
eyedeekay
I'll post my test matrix up on the gitlab issue before I close it
eyedeekay
I have a branch off the 2.6.0 release containing just the css fix which I can tag and do a point release against
zzz
I don't know if you want to do a release, but if you do, I'd rather it be from master than a branch, because we've never done that and releases should be tagged in master, for the downstreams
eyedeekay
OK I can tag that instead if need be
eyedeekay
Re: schedule: how is mid-September for 2.7.0, early-December for 2.8.0?
zzz
but that means holding off checking in anything we don't want in the release
zzz
how many weeks to mid-Sept?
eyedeekay
About 9
zzz
that's pretty tight
eyedeekay
If we were to release on the 19th again, it's about 9
eyedeekay
Yeah
zzz
if you split the difference between now and christmas it's more like early Oct. I think
eyedeekay
Yeah I think you're right
eyedeekay
I'm going to be travelling on the 1st and 2nd of October, so maybe the 2nd week of October for now
eyedeekay
Possibly October 8
zzz
see what i2pd wants
eyedeekay
OK, pinged them over on #i2pd-dev
zzz
if you do decide to do a 2.6.1, what else would you want in it? Any of my MRs? I also have the izpack translation fix ready to go...
eyedeekay
If you've got an izpack translation fix ready to go I definitely would like to put that in a 2.6.1 release, and I see no good reason not to include the translation status page in either, noscript errors have me a little nervous about svg though
eyedeekay
So translations MR's yes, svg no for now
zzz
I'll double check svg w/o js, but since they're <img> and not <object> it should work fine
zzz
the susidns svg is <object> which is why noscript gives it the snake
eyedeekay
Oh good I am still going to double check myself also, but that's good to know
zzz
confirmed, svg <img> fine w/o js
zzz
you want the izpack fix as a MR or straight-in?
eyedeekay
Go ahead and do it as a regular checkin
eyedeekay
And as long as svgs work as <img>s when noscript is enabled go ahead and merge that one too
zzz
ok I'm gonna wait on everything until you check in the css fix, let me know
eyedeekay
CSS fix and the debian changelogs are now checked in
zzz
thx, guess my vacation is over ))
dr|z3d
<img src=...svg should be fine without js, it's tor browser and anything that has svg disabled that breaks display.