#i2p-dev (irc2p) | 2.10.0-10-rc | Network status http://zzz.i2p/topics/3714 | See important notes on zzz.i2p before updating | New beta site please review http://g5hrmnatotkavda5nnalr74ecvu44vigutrcb7h3qbrmsfdmoora.b32.i2p/ | Prop. 169 review Feb. 10, 8 PM UTC #ls2

orignal when the release? next week?

zzz don't know, ask eyedeekay. We haven't had our tag freeze yet which is usually 12 days before

zzz to all: update on the transifex/weblate thing. I had my call with Loc. Lab.

zzz they're moving mostly because of cost. OTF was paying TX an enormous amount

zzz it would cost us est. $6K/year to stay

zzz Tor moved 2 years ago. Nobody is staying on TX.

zzz They aren't migrating our data. They are just setting up a blank project and then it's our problem, although they will provide some guides

zzz I can't find how to fully migrate the TX CLI config file to the weblate config file, and this Loc Lab guy isn't familiar with CLI

zzz OTF hasn't told TX yet we're leaving, but they stopped paying. So we can't yet poll our translators for what they want to do yet because it isn't public

zzz so I think we gotta move, but we'll use tx for this release, then we'll have 3 months to figure it out

zzz Loc Lab and us can use it as an opportunity to try to get renewed translator attention on our project, the activity has really been declining over the last couple years

zzz they will tell us when they set up our project and when the move is public and when tx pulls the plug

zzz EOT

eyedeekay Regarding release time, I've been trying to figure that out myself pending some review of the past month's checkins. I see two paths:

eyedeekay 1) If the changes that have been checked in this month in Java I2P have been adequately isolated or can be considered non-major, then we should freeze tags on the 28th and release on the 9th

eyedeekay 2) If the changes that have been checked in this month have been major and/or must be activated un-conditionally on the live network, then we should push back a month, freeze on the 19th, go on the 2nd

eyedeekay It seems to me that the stuff you've been discussing in IRC has not been checked in directly to that's not much of an issue

zzz nothing major. the concern is jetty 12 testing. I won't push any NTCP2 PQ stuff until after both the release and the prop. review

zzz I need to upload test debs to launchpad for all the flavors so I can fix that stuff before you hit it

eyedeekay Yeah jetty seems like it's been fraught, and that would be massively helpful if you can test the deb builds before the release

eyedeekay Do you have a PPA outside of i2p-maintainers where those builds could become available? Either timeframe is fine with me.

zzz been on my list, set a release date to motivate me ))

zzz libjetty12 made it into resolute 26.04 so need to make a resolute flavor

zzz this is my PPA launchpad.net/~zzz-i2p/+archive/ubuntu/test

eyedeekay OK. Then given what I know I'm going with 1) freeze on the 28th and release on the 9th

zzz ok, i'll get crackin'

eyedeekay If it turns out to be a mess let me know if you need more time, if it turns out well we'll chirp about the PPA for testers

orignal guys we need a definite time

orignal some aggangements etc.

zzz not expecting major problems, so it's the 9th

orignal so postponed 2 weeks?

orignal because initially we agreed about end of January

zzz I don't know what you and idk agreed to previously, so whatever you say, thats what it is

orignal it was mentioned here

orignal we can wait

zzz or you can debate it with him, or release whenever you wish

orignal we want to change version

eyedeekay The last time we talked about it before I had travel we said it would be the beginning of February

eyedeekay If we froze tags tomorrow the earliest we could go is the 3rd of February, and I don't think we should turn around and freeze tags tomorrow

orignal again we need a deifinte answer that's all

eyedeekay February 9th

dr|z3d as I said before, bring the translation backend in-house, run it on your servers. no one to rely on, no one to pull thr rug.

dr|z3d as for coverage, 100% for all 30 translations in + :)

dr|z3d *launguages

dr|z3d *languages

dr|z3d *** blames orignal for his typing. ***

dr|z3d as for the dates, last time release was floated, it was end of jan or first week in feb. so we're not far off.

dr|z3d I also remember saying that Tor would probably migrate from transifex and self-host. Is that what they're doing?

orignal dr|z3d right

orignal but 9-th is the second

dr|z3d what's a couple of days between friends? :)

orignal the first week start on feb 2

dr|z3d well, no point pontificating, we've got a firm date now, the 9th.

orignal unless it's postponed again

dr|z3d zzz's confident enough to state that it won't be, so fix your sights on the 9th.

orignal <eyedeekay> 2) If the changes that have been checked in this month have been major and/or must be activated un-conditionally on the live network, then we should push back a month, freeze on the 19th, go on the 2nd

dr|z3d <zzz> not expecting major problems, so it's the 9th

orignal what if major problems

dr|z3d he's already done most of the work, so I'd trust him when he anticipates no major problems. the major problems / headaches he's already slayed, right zzz?

eyedeekay There's only 5 checkins, all minor, everything I would be concerned about is isolated to branches and not going into the release

eyedeekay So there will be no major problems. It's the 9th

dr|z3d *** tattoos "the 9th" on orignal's forehead. ***

orignal guys if we knew you were so unserious about release dated we would make a release in december

orignal if you say last week of January or first week of February you shoulfd hold in it

dr|z3d these things are always subject to adjustment, orignal. no big deal, there are more important things to make noise about.

dr|z3d take the extra time to add some missing features to i2pd :)

orignal adjustment between two date sounds resonable

orignal again it's not about me

orignal R4SAS needs to allocate his time

dr|z3d like, does i2pd permit the user to specify multiple http proxies and randomly choose one, ignoring any for the session that aren't up?

orignal you can specify as many http proxies as you wish

dr|z3d for a single port?

orignal no

dr|z3d Blinded message

orignal we don't do round-robib in any places

dr|z3d well, there's a missing feature you may want to implement.

dr|z3d (or not).

orignal not now