1) I corrected the spelling of my first name above, 1 L, 2 P, thanks. ;-)

2) This work is not finished. In fact the list of caches will need to be updated regularly (we can see that it should be updated at least once each month, in beta versions, and make sure that a release version contains the latest working list. If a release has been published more than 2 months ago, there should be a minor update to the release branch to update that list in the donwloadable distribution. It is not necessary to advertize this minor sub-version if there's no other significant protocol implementation update or GUI bug correction. So people that have version M.n.x should not be asked to update to version M.n.y, but they may be informed if a version M.(n+1).* is released. Such information should then be displayed automatically on version (M+1).*.*

Downloadable beta versions should also expire after 2 months (so that the user downloads a newer beta, with bugs corrections and performance updates or a release): we've seen that a new component in a beta may cause unexpected problems on the network for its scalibility or on the resources of some other servers on the web.

For CVS version users, the same policy should apply: a user should update its sources to get the new update.ver file at the same time. If a user forgets to get the complete updated sources, the update.ver will expire and beta tests will no longer be helpful as their results will be too old. Some bug corections are essential for a release (some releases will discard temporarily some new components that still don't work as expected, before they get reintegrated in the development branch with their corrections).

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml