<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 20, 2012, at 7:13 AM, James A Simmons wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Thu, 2012-07-12 at 15:37 -0400, Nathan Rutman wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 12, 2012, at 7:30 AM, John Carrier wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">A more strategic solution is to do more testing of a feature release<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">candidate _before_ it is released. Even if a Community member has<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">no<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">interest in using a feature release in production, early testing<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">with<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">pre-release versions of feature releases will help identify<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">instabilities created by the new feature with their workloads and<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">hardware before the release is official. <br></blockquote></blockquote><br>...<br><blockquote type="cite">So, it seems, we need to test pre-release versions of Lustre, aka<br></blockquote><blockquote type="cite">Master, with my applications. To that end, how willing are people to<br></blockquote><blockquote type="cite">set aside a day, say once every two months, to be "filesystem beta<br></blockquote><blockquote type="cite">day". Scientists, run your codes, users, do your normal work, but<br></blockquote><blockquote type="cite">bear in mind there may be filesystem instabilities on that day. Make<br></blockquote><blockquote type="cite">sure your data is backed up. Make sure it's not in the middle of a<br></blockquote><blockquote type="cite">critical week-long run. Accept that you might have to re-run it<br></blockquote><blockquote type="cite">tomorrow in the worst case. Report any problems you have.<br></blockquote><blockquote type="cite">What you get out of it is a much more stable Master, and an end to the<br></blockquote><blockquote type="cite">question of "which version should I run". When released, you have<br></blockquote><blockquote type="cite">confidence that you can move up, get the great new features and<br></blockquote><blockquote type="cite">performance, and it runs your applications. More people are on the<br></blockquote><blockquote type="cite">same release, so it sees even more testing. The maintenance branch is<br></blockquote><blockquote type="cite">always the latest branch, you can pull in point releases with more bug<br></blockquote><blockquote type="cite">fixes with ease. No more rolling your own Lustre with Frankenstein<br></blockquote><blockquote type="cite">sets of patches. Latest and greatest and most stable.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Pipe dream?<br></blockquote><br>Since people are now moving to help test out the current master branch<br>for whamcloud I like to purpose posting a general summary of testing<br>results people are seeing. I personally have finished a first run at<br>testing 2.2.91 this last week and would galdly share the results. Anyone<br>else can to share :-)<br><br><br></div></blockquote></div><br><div>I started a page on the <a href="http://www.opensfs.org/foswiki/bin/view/Lustre/WebHome">OpenSFS Wiki</a> for everyone to share their <a href="http://www.opensfs.org/foswiki/bin/view/Lustre/TestResults">test results</a> in a free-form format. Note that the Wiki itself is still in it's infancy - I call on the community to help populate it.</div></body></html>