> Is there any verification of the contents of the tar balls being done?
That is a bit snide, don't you think? Yes, there is a check, after they start mirroring. Then the "sets" files are fixed, and snapshots are rebuilt. Sometimes the files are already moving along the mirror path... That's a process which works for me, and works for the developers. The output of this process is called snapshots; it is not called a daily releases, and there is no warranty or any statement of suitability for any purpose. Most are built by me, using a mixture of handheld and dynamic procedures, and are simply a SIDEEFFECT of updating machines and ensuring the tree is in good shape, and once every 6 months this is important so that we can make a good release. So really, what do you expect? I am asking, because you seem seriously dissapointed. Do you expect a high-quality CDN delivery environment that gives you 1-2 snapshots per day (as now) -- but globally -- at high speed? And for the contents to be built with extremely high assurance? Sorry, if that is what you want, your expectations are out of line. Noone is paying for that to happen. Most of our users are precisely like you -- not providing a single cent to back their demands that requirements be improved. Furthermore, this is a research operating system project, it is not a commercial product, and it is not operated to meet commercial customer values, since the price point is kept at precisely zero. Not anything charged for access to sources, snapshots, documention, ideas -- NOTHING. So I could stop building snapshots, and get right on the task of building such an environment for you! Actually I won't, because I don't take instruction from people who aggressively point fingers at people who gave it away in an imperfect way. Kindly note the lack of a warranty or promise, and adjust your attitude a little.
