We need to get a stable build out based on trunk in the near future, with 
nextgens' compression changes and sdiz's refactorings. The former is 
obviously a good thing, provided it can be debugged properly (and it may need 
some tuning). The latter is also good, having provided us with a fix for a 
*major* announcement bug. However, can we please have some sort of a 
tentative feature/refactoring freeze please? Just until we get a build out 
with these changes in? We have a couple of important bugs in trunk:
- Running out of fd's. This is definitely serious, but nextgens hasn't been 
able to reproduce it.
- A client layer bug where we add blocks after we have finalised. This could 
be serious or could be trivial.

Also, some work needs to be done on plugins; many of the recent reports of 
connectivity problems appear to be caused by losing the UPnP and JSTUN 
plugins:
- Make them more stubborn. Keep trying to load a plugin on startup even if it 
fails once.
- Display a user alert if we have no IP detection plugins, and don't have an 
IP override or locally detected address either. Provide a means to 
permanently dismiss this via a config option, if the user knows what (s)he is 
doing.
(Yes I know this isn't strictly in keeping with a freeze, but it's the most 
serious bug we have to deal with at the moment in trunk apart from the above 
two issues).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20081106/8dcff2a0/attachment.pgp>

Reply via email to