Page 1 of 1
I2P 2.6.0 Schedule
Posted: 22 Apr 2024 18:29
by eyedeekay
I2P 2.6.0 Release Schedule:
- Target Release Date: July 19 2024
- Checkin Deadline Date: July 15, 2024
- Major Changes Deadline: June 15, 2024
- Tag Freeze Date: July 3, 2024
Planned Changes:
- SSU1 Removal
- Susimail Search
- Browser Proxy
- Bugfixes and improvements, see also Roadmap
The master branch from git will reflect the code which we are running and testing.
Re: I2P 2.6.0 Schedule
Posted: 22 Apr 2024 19:38
by eyedeekay
If you like living on the edge, continuously built dev-builds(which are generated by github) are now always available at
https://i2p.github.io/i2p.i2p/i2pupdate.zip
These are continuously generated dev builds built from the tip of the master branch, they are always the latest code which will successfully compile(with javadoc). They are generated by Github CI. Only use them if you want to help test dev builds and can tolerate the risks associated with those facts.
Re: I2P 2.6.0 Schedule
Posted: 23 Apr 2024 11:17
by zzz
SSU2 removal?
Re: I2P 2.6.0 Schedule
Posted: 29 Apr 2024 21:06
by eyedeekay
Oops, SSU1 removal, changed above.
Re: I2P 2.6.0 Schedule
Posted: 02 Jun 2024 12:54
by zzz
I believe that for people to configure their router to automatically update to dev builds (which also requires routerconsole.advanced) you would need to provide the i2pupdate.zip file at an in-net URL.
Re: I2P 2.6.0 Schedule
Posted: 12 Jun 2024 16:05
by eyedeekay
Indeed. It is now available in-network:
Code: Select all
http://edpiihbz4xebluzqmuuerxa4fl633oktxdtqceb3kjsm6ouvbaaa.b32.i2p/i2p.i2p/i2pupdate.zip
http://edpiihbz4xebluzqmuuerxa4fl633okt ... a.b32.i2p/ actually points at i2p.github.io:443 so anything that goes onto our github.io will also be visible there, for instance there is up-to-the-build Javadoc at:
Code: Select all
http://edpiihbz4xebluzqmuuerxa4fl633oktxdtqceb3kjsm6ouvbaaa.b32.i2p/i2p.i2p/
In order to use these dev builds automatically, you can:
- Open your router.config file in a text editor
- Add the line: routerconsole.advanced=true
- Go to the updates menu: http://127.0.0.1:7657/configupdate
- Check "Update with unsigned development builds?" true.
- Add the URL to the "Unsigned Build URL" field: http://edpiihbz4xebluzqmuuerxa4fl633okt ... update.zip
OR, manually: use:
Code: Select all
export I2P_DIR=your_i2p_install_directory
export http_proxy=http://127.0.0.1:4444
export https_proxy=$http_proxy
wget -O $I2P_DIR/i2pupdate.zip http://edpiihbz4xebluzqmuuerxa4fl633oktxdtqceb3kjsm6ouvbaaa.b32.i2p/i2p.i2p/i2pupdate.zip
i2prouter graceful && i2prouter start
Re: I2P 2.6.0 Schedule
Posted: 16 Jun 2024 16:00
by eyedeekay
Yesterday was major changes deadline day, the deadline is now closed. Minor changes and bugfixes will still be accepted. Right now the goal is test, test, test, which should be easier for more people to do per the unsigned update URL above. Please report bugs here(on this thread is OK) or on Gitlab.
As of now we are still on-schedule. If we need to do another big change we'll have to stop the presses and set a new deadline, but I don't anticipate needing to at this time.
Re: I2P 2.6.0 Schedule
Posted: 21 Jun 2024 20:29
by zzz
For my planning, please coordinate with i2pd and set a release date. Thank you.
Re: I2P 2.6.0 Schedule
Posted: 27 Jun 2024 18:07
by eyedeekay
Release date is the 19th of July, post updated above.