We can set a time limit for when the min known good build increases to the build # of 0.5.1. Basically, we keep our current minimum and before we release, we set a date (say we released today, we'd set the date at the 29th of january) at which point the minimum build increases automatically to the new one.
This would allow for the network to upgrade gracefully from the older builds to the newer builds without requiring the users to upgrade multiple times and would also most likely get the minimum known good build to increase all at once so we can have a more virgin network to test with. Also it would enable the entire network to be ARK enabled which will most likely increase the size of the network (since I will make the windows configuration program atleast pick up on the transient setting and double check with the user that they *really* want it to be transient). All in all we probably are going to want to increase the minimum build, and this seems like a more graceful way of doing it than the other major ways. Thoughts? -Mathew _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
