the-me wrote:Okay, I'm getting it (blurry? you bet!). So I have written a little summary about what I think I know know
Well you're getting close
... [list]
[*] as far as I know the core trunk will be converted - in a mid-term time range - from holding the complete suite to holding the standalone applications, so firefox, thunderbird, etc. will become the core trunk, and the whole suite will not be developed any longer (except maybe in separate branches)
This point in your list and the couple that follow aren't quite right. The trunk and each branches all have all of the code for the complete suite as well as the standalone applications (and also a bunch of other stuff). When someone makes a build, they specify which program they are trying to build, and the build process takes the right bits of code for that program.
[*] builds from the AVIARY tree should be labeled just so, because they're not a branch build (which would be 0.8+), neither a trunk build (which would be from the core trunk)
one last question is remaining: with a branch firefox build, which tree is taken? this should be - to my understanding - the release version of 0.8 just with more patches applied, right?
"a branch build" isn't a specific term. A while ago, people would probably have been talking about the Firefox 0.8 branch, which ended when Firefox 0.8 was released. After that, they probably would mean a Firefox build from 1.7 branch. If anyone says it now, they would probably be talking about the aviary branch. "branch build" is a general term which can apply to any branch. However, there is usually just one branch which is of interest, so if someone talks about "a" branch build, it's usually obvious that they are talking about the branch that's currently being used most.
. I tried one of the M3 optimized builds from Moox, and I see it has no installer. It works fine, but the problem is some extensions are not working since it was never really "installed". Does anyone know a way around this please?
I previously had .9.3 on this PC and just overwrote it in the Program Files folder with the contents of the Moox build, same thing. I'm going to install a new HD in the next day or so, so it's not that big of an issue now if something gets screwed up. However on the new HD I'm still going to have to figure out how to get this Moox build "installed". I emailed him early today, will see what he says if he replies. I'll add this info to the thread.
