Since providing imagefiles has been a touchy subject in the past -- particularly with ISO images, I'd really like a clear cut answer before altering the current state. AFAIK: 1st, the alpha1-candidate will * gcc2hybrid, * ISO, VMDK, raw Image. * built using the "alpha-*" ReleaseBuildProfiles (which will dictate optional packages and possibly ATA vs IDE) * not --include-gpl-addons Now, for the other gcc combinations of gcc2, gcc4, and gcc4hybrid, what should be done about them? * continue providing them as "alpha-*" (or a similar profile to be created, eg "nightly-*") * provide them as only the basic raw image * provide ISO's of them? (be it either basic haiku-cd or @alpha-cd) Should haiku-files.org be restructured? * creating haiku-files.org/releases/R1Alpha1/index.php * relocating haiku-files.org/raw, /vm to haiku-files.org/nightly/raw, /vm, /iso(assuming we want to provide nightly iso's) * modifying haiku-files.org/index.php to reflect the above changes Lastly, if no one objects, i'd like to start providing gcc2hybrid images of ISO, VMDK, Image. One set with IDE and another with ATA -- as this should help to flesh out the issues between them. Though, i'm not sure if they should go in a new location, eg, haiku-files.org/releases/R1Alpha1Candidate/ --mmadia