and to make things even more confusing we will be using a custom spin for GPA that has the backup code and more drivers installed! Ham is working on the latest version tonight and will have a fresh iso for us to download in the morning.<div> </div><div>Thanks! <div class="gmail_quote">On Sun, Sep 6, 2009 at 11:44 PM, Bill Bogstad <<a href="mailto:bogstad@pobox.com">bogstad@pobox.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> As I get more involved in making SoaS boot in various weird ways in weird hardware environments, I've found the wiki pages and the various download directories to be a little disorganized. I think that part of this is because SoaS is fundamentally a different product from Sugar itself in a way that isn't being acknowledged. As I see it; Sugar, like most free software projects, delivers source code and related materials (documentation, etc.). Those deliverables will be used by pretty technical people to produce binaries. Git and/or carefully generated source code tar balls works for this kind of user. SoaS is a (fedora based) Linux distribution whose GUI is Sugar. SoaS deliverables are binaries (in various forms) as well as installation instructions. People will download and run SoaS directly. Hopefully, many of those people won't be technical at all. I don't think SoaS has good release management on its deliverables yet. I'm not sure how to get across my general concerns, so I think I will point out two specific issues: 1. The various SoaS wiki pages make no real attempt to differentiate between Strawberry instructions/file references and generic SoaS descriptions/features. A new SoaS release is coming soon and it's not obvious how the instructions/files for this release will be kept separate from Strawberry in the wiki. 2. The 'release' download directory isn't structured to keep released/beta versions separate. There also seems to be multiple versions of the livecd-iso-to-disk.sh file floating around. I'm pretty sure that the version which can be found there now is different from the one I originally downloaded with the Strawberry ISO which is different from the one which is embedded in the Strawberry ISO image. The head of the Strawberry branch of this file in git is not what is currently being distributed next to the Strawberry ISO. The bad news is that I can't think of any way to use git to keep track of this for us. It will probably have to be done semi-manually. The good news is that, except for daily builds, there won't be that many different versions that need to be managed. Oh, and can we add a new naming scheme? The next release of SoaS should also be called SoaS 0.86, not just bratwurst or melon or whatever. It should be obvious from the name which version of Sugar is included. We can have still have cute names as well as boring numbers. We'll just have both (like Ubuntu does). Thanks for your attention, Bill Bogstad _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div> -- Caroline Meeks Solution Grove Caroline@SolutionGrove.com 617-500-3488 - Office 505-213-3268 - Fax </div>