-The 0.8.13 release contains several bug fixes and a couple of new features. -We are pleased that the last release significantly improved performance, -and the network is running well despite continued rapid growth. +In the 0.9 release we migrate to Jetty 6 for the console and eepsite web server, +and introduce a simplified router console home page. +This release is network-compatible with prior releases, however see below for important +information on compatibility with existing eepsites, plugins, and webapps. Upgrading is recommended. -
-This is likely to be the last release before 0.9, in which we will migrate to Jetty 6, -and introduce a simplified router console home page. Monitor the news section of -your the router console in the coming weeks for more information on the next release. -
-Starting with this release, the router will -check for and install plugin updates shortly upon restarting after a router update. -To prevent this, add the advanced configuration -plugins.autoUpdate=false before restarting. -There is also a new update-all button on the client configuration page. -
-Routers in certain countries will now automatically enable hidden mode for increased protection. -However, hidden mode may have lower performance or reliability, and is still a work in progress. -To disable hidden mode before restarting, add the advanced configuration -router.isHidden=false. -To disable hidden mode later, select use all auto-detect methods under IP Configuration on the -network configuration page. -For the list of countries see this thread on zzz.i2p. -The only country on the list that has more than one or two I2P users is China. -
-After you have upgraded, check out the new tunnel creation wizard. +
+ +Update info
+ +In-network updates and new installs will include Jetty 6, Tomcat, and JSTL. + PPA (Ubuntu/Debian) updates will have new dependencies for these packages.
+ +If you have not enabled or modified your eepsite settings, the update should automatically migrate you to Jetty 6. +If you do not use Jetty for your eepsite, the update will not affect it. +
+ +If you have more than one Jetty eepsite or you have changed the local port (7658 by default) or otherwise edited jetty.xml, + you must manually edit the new jetty configuration files after updating, and then restart.
+ +For those with Jetty-based eepsites, we recommend that you verify that the upgrade +was successful and the eepsites are operational after the router restarts. + +
Plugin information:
+
Plugins not listed below should continue to work under Jetty 6.
+
The following plugins require updates for Jetty 6. The router will download and install them a few minutes
+ after upgrading: i2pbote, pebble, zzzot
+
The following plugins have been renamed and for Jetty 6. Users must manually remove them and download the new versions
+ after upgrading: neodatis, seedless
+
Other non-standard console and eepsite webapps not packaged by the I2P development team may or may not + require modifications.
Say hello to the volunteers on the #i2p-help IRC channel. Get involved, diff --git a/router/java/src/net/i2p/router/RouterVersion.java b/router/java/src/net/i2p/router/RouterVersion.java index 931fb7af41..a411b00998 100644 --- a/router/java/src/net/i2p/router/RouterVersion.java +++ b/router/java/src/net/i2p/router/RouterVersion.java @@ -18,7 +18,7 @@ public class RouterVersion { /** deprecated */ public final static String ID = "Monotone"; public final static String VERSION = CoreVersion.VERSION; - public final static long BUILD = 28; + public final static long BUILD = 0; /** for example "-test" */ public final static String EXTRA = "";