At 12:00 PM -0800 12/11/06, [EMAIL PROTECTED] supposedly scribed: >Or use the branch builds, which have all of the Camino-specific >improvements that are being developed for 1.1. Since almost every >Camino change at this point is being added to both the branch and the >trunk, there's really no reason for most people to use trunk builds >(unless they have a burning desire to see the Acid2 test passing). >The entire point of the branch builds is to have a stable development >platform. > >-Stuart
Indeed, except there has been an issue of identifying which is a branch build and which is a trunk build. My first assumption is that we are talking about the "nightly" folder. For as long as I can remember, all files to download are uniformly called "Camino.dmg." So one needs to rely on the folder name. I think it was only a month or so ago when I last checked, I think 1 folder actually said "trunk" in it's name. Just checked and it seems a lot of folders have "trunk" added. This is good. But CAN we assume that any folder that does NOT contain a trunk release is a branch release? And, what version is contained in the following folders, each one populated today? 2006-12-10-22-1.0-M1.8.0 latest-1.0-M1.8.0 2006-12-11-02-1.1-M1.8 latest-1.1-M1.8 While there MAY be clues, they don't make sense. Why would something with yesterday's date be different from something when today's date when both are generated today? Why would a "latest 1.0..." be posted at the same time a "latest-1.1..." is posted? I see there's a ReadMe from 2004 that obviously contains information that has NO elation to what is being posted. Why can't a readme that actually tells us what is what be posted into this directory? I can't imagine this would pose some form of huge imposition to those who know and can post such a file... _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
