Can anyone explane me all those repositories?
Nomis101
for my own trunk builds. But since a few weeks (maybe since
mozilla-2.0 branched) I've noticed, that instead of mozilla-central a
lot of patches checked in into projects/build-system and projects/
cedar and then get merged into m-c. But what is build-systems and
cedar for? Are this some kind of "try repos"?
Than I'm confused because there are now also mozilla-aurora, mozilla-
beta and mozilla-build. Whats that for??? I'm now confused which
repository I should use for my build.
(At the moment I use a patched version of mozilla-2.0, which seems
safe to me)
Benjamin Smedberg
probably read that newsgroup to stay informed. There are a bunch of
different questions here, so here are some links to some answers:
Description of mozilla-central, mozilla-aurora, mozilla-beta and the new
rapid-release model:
https://wiki.mozilla.org/RapidRelease
mozilla-central serves the same purpose it always has, as the primary
place in which new features are landed for integration testing and
nightly user testing. If you used mozilla-central before, you should
probably continue to use it.
The other repositories you asked about (build-system and cedar) are
project repositories. We are planning on having more project
repositories (in general), so that people can work on larger projects
and get tinderbox testing before landing in mozilla-central. In
particular, cedar has been a temporary place to get tryserver-like
testing during this short cycle for Firefox 5.
--BDS
Joshua Cranmer
A better person than I would have links to all of the explanations for
this (if you follow m.d.planning, it would actually be quite hard to
have missed all of this information), but this is what I have:
mozilla-central: The trunk, most bleeding edge version of Mozilla code
projects/: A series of project repositories, much akin to the
mozilla-central/tracemonkey setup. Basically, a relatively recent
version of mozilla-central with newer changes to the appropriate
projects landing here instead of on mozilla-central; occasionally, m-c
will be merged with the repo and v.v.
build-system: Changes to the build system, e.g., remove --disable-ipc
from configure
graphics, devtools, etc.: Specific repos
cedar: A "temporary" project branch, currently being used as metering
check-ins for mozilla-central.
birch, maple: Other "temporary" project branches. Don't know current use.
mozilla-aurora: A less bleeding but stabler version of Mozilla, to which
m-c is merged every 6 weeks or so
mozilla-beta: The next level up from mozilla-aurora
I think that if you just want general "trunk" code, mozilla-central
would be best.
Nomis101
is for, but I've wondered about all the other (new) repos. I've never
read in mozilla.dev.planning before, so it seems I missed a few
things. Thanks for pointing me to mozilla.dev.planning.
Robert Kaiser
> But what is build-systems and
> cedar for? Are this some kind of "try repos"?
"Project branches", mostly, there are actually ones for the JS engine
("tracemonkey") and "places" as well, possibly others. Those are
something between try and mozilla-central - a certain project or set of
patches lands there (with reviews), is being tested and refined, and
once everything is fine there, that "project branch" is being merged
into mozilla-central. That way larger work can be done and stabilized
without breaking mozilla-central.
> Than I'm confused because there are now also mozilla-aurora, mozilla-
> beta and mozilla-build.
mozilla-build is the Windows build tools needed in addition to MSVC to
compile Mozilla stuff on Windows. The other have been explained by other
people here and belong to the new rapid release process. :)
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community needs answers to. And most of the time,
I even appreciate irony and fun! :)