<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Thank you kindly Kyle. We have tried to have a long-running testing environment since last summer and have a combination of testing and community building going on continuously.<br><br>This multiple root inventory issue is something that has plagued us for a while. One of my current thrusts is to find a way to clean our database without re-initializing it. <br><br>Many folks like unit tests. Personally, I find that one can move faster with system tests of a running system as one is able to sort out the "wheat from the chaff". There are some times this is possible, some times it is not. <br><br>In any case, thanks for the vote of confidence. It makes me feel
that this effort of updating OSGrid every single day and working with hundreds of region owners, thousands of users and nearly 100,000 assets is useful to the project.<br><br>Charles<br><br>I wholeheartedly agree. The two goals (cleanliness and insight) are<br>not mutually incompatible.<br><br>Alpha-time is the time when the greatest insight is needed into how<br>the designs behave. If a given design causes problems that violate<br>the constraints of the environment, some aspect of the design needs to<br>be changed BEFORE the code goes to beta (or worse, release).<br><br>If you like, you can think of it as a means of obtaining test<br>information from long-running tests, as opposed to unit-testing single<br>discrete units of functionality. (Not that OpenSim has much of that,<br>either.) If you can create a clean design for integrating run-time<br>gathering of statistics, then you've solved one of the main problems<br>that
eventually integrates alpha-quality code and design into beta or<br>release software.<br><br>I'm specifically thinking OSgrid with my suggestion -- but there's no<br>reason it couldn't be made into a developmental tool to figure out<br>when and how things break when the code is changed. It also allows<br>for useful identification of when problems were introduced. (In fact,<br>since OSgrid is OpenSim's largest-scale and longest-running tester,<br>such insight being made available can only help speed development.)<br><br>-Kyle H<br>_______________________________________________<br>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev@lists.berlios.de" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br></div><br></div></div></body></html>