20:00:25 0) Hi 20:00:25 1) Tails maintainer (zzz) http://zzz.i2p/topics/2108 20:00:25 2) 0.9.30 update (zzz) 20:00:25 3) UI branch status - for .30 or .31? (str4d) 20:00:25 4) Jetty 9 branch status - for .30 or .31? (zzz) 20:00:30 0) Hi 20:00:32 hi 20:00:50 Hello 20:00:54 1) Tails maintainer (zzz) http://zzz.i2p/topics/2108 20:01:16 as most of you know, tails and I agreed to remove i2p from tails 20:01:34 this will take effect in tails 2.12, due out in abut 6 weeks 20:01:43 hi 20:01:57 ok 20:01:59 sad, but we had no other choice. If we get a volunteer to maintain it, we will reapply 20:02:08 anything else on 1) ? 20:02:45 to bad, but not to be changed soon (tm) 20:03:07 Yeah. Too bad the guy at 33C3 didn't work out 20:03:30 yup 20:03:40 2) 0.9.30 update (zzz) 20:04:23 ok we're a week from the .29 release, our plan is for a standard 8-week cycle. Big changes in by mid-March, release late April 20:04:51 there's a couple big props pending that we will cover in 3) and 4) 20:05:17 anything else on 2) ? 20:05:51 I´ll be gone 1st may 20:06:00 or better 30thapril-2nd may 20:07:00 both of these props are important because it's difficult to go back. once we prop them, we have to get them to work before we can releawe 20:07:07 *release 20:07:29 yeah 20:07:57 3) UI branch status - for .30 or .31? (str4d) 20:08:34 this is an enormous change, although originally advertised as a minor refresh, and part 1 of several to update the console UI 20:08:54 the diff is 77K lines, with 500+ files added, 200+ files changed 20:09:06 I would vote for 1 prop per release, not both in .30 20:09:07 str4d, what's the status, and do you want to prop it for .30 ? 20:09:27 and as jettty9 is more important, push ui to .31 20:11:07 the key is we don't want to prop something if the author doesn't have time to fix problems before the release. Otherwise the release could be delayed indefinitely 20:11:39 yeah 20:11:46 so whenever it's propped we need assurances from str4d that he will be available here to respond to issues 20:11:54 str4d, what are your intentions? 20:12:15 is str4d around at all? 20:13:11 dunno. I think this branch really got away from him, advertised as minor but became massive. I think he's been working on it for a year. 20:13:38 I guess we'll have to follow up with str4d later 20:13:54 anything else on 3) ? 20:14:03 He did say something about a branch recently 20:14:17 I have not tested it, I'll clone it 20:15:23 it's... interesting. I'd say he went in a different direction from what I've been doing in the last several years. I can't predict what the general reaction will be. 20:15:42 anything else on 3) ? 20:16:16 4) Jetty 9 branch status - for .30 or .31? (zzz) 20:17:03 this is about 3k lines of diff. I have the standard builds working in my branch, and the build for stretch. I haven't tested the down-rev builds for wheezy/precise/jessie/trusty yet 20:17:35 the pressing thing is that stretch won't have jetty 8. It appears that zesty, due out next month, won't either, unless it appears in backports 20:17:44 but jetty 8 was eol in december 20:18:17 jetty8 will less likely appear in backports 20:18:20 so the risk is that stretch or zesty will be released, and i2p won't work in them 20:18:42 so I propose to prop my jetty9 branch in the next week, to be included in .30 20:19:21 yeah 20:19:29 this will break, at least, the following plugins: bwschedule, i2pbote, i2pcontrol, zzzot. They will need at least a recompile, maybe a rewrite 20:19:33 thats what I propose, IF youu think you can do it 20:20:46 I can recompile zzzot. Up to the authors of the other 3 (cacapo. str4d, hottuna2 respectively) if they can release 20:21:40 I can do my side 20:22:07 I think if we wait until .31 in june/july there will be a lot of unhappy package users 20:22:53 yeah 20:22:54 so I plan to prop it in the next few days 20:23:00 anything else on 4) ? 20:23:08 I will test 20:23:28 anything else for the meeting? 20:24:25 * zzz warms up the baffer 20:24:30 not that I know of yet 20:25:27 * zzz *baffffs* the meeting closed