On Mar 29, 2007, at 1:50 PM, paulc wrote: > Ah, my preference normally was to go to the ftp site. But it still > continues to be confusing.
We post the nightly link on caminobrowser.org to make it easy to get the latest nightly, as has been explained on this list before; continuing to use a system that you find confusing instead is a personal choice. > Here are the possible folders a "current branch build" may be found > in: > > latest-1.1-M1.8 > 2007-03-29-01-1.1-M1.8 One always has the build from 2007-03-29, since builds are archived for regression testing, and one always has the latest build, for convenience. > Reminds me, curious about what point is reached when a branch is > "frozen" off the trunk? Is it when a particular build is considered > "released?" Branches aren't frozen; they continue to change, which is the point of making them. A Gecko branch is made when the core developers want to start pushing toward a stable Gecko release. > And does that get a unique version designation (I've seen > guys carry the same version number, but different build numbers and > there ARE code changes between the two!). Gecko branches always have distinct Gecko version numbers. Product (Camino, Firefox, Thunderbird, etc.) version numbers are not directly tied to Gecko version numbers. -Stuart _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
