Re: Mozilla version control requirements and git
- From
Jon Smirl <jonsmirl@gmail.com>
- Date
- Sep 4, 2006, 01:43 UTC
- Message-ID
- <9e4733910609031843y79750bfcka5f0c350a6b24c9c@mail.gmail.com>
- In-Reply-To
- <46a038f90609031440s33e66499x51026aa6062566d2@mail.gmail.com>
On 9/3/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:
Show 14 quoted lines
> On 9/4/06, Jon Smirl <jonsmirl@gmail.com> wrote: > > You can't really fake it. Many of the projects in Mozilla are > > dependent on each other. If you break them up into separate > > repositories you lose the ability to do a cross project commit. This > > is common when you are changing an interface between the subprojects. > > In many projects this is handled by having tags and generally > versioning modules and interfaces. Being independent gives the > subprojects/modules a lot more freedom to work/branch on wild > tangents, and the versioned interfaces mean that -- with the > contraints of the versioned interfaces -- you can mix and match > branches/releases of the different subprojects. > > In short, I'd definitely break those up :-)
Mozilla always ships as a complete system so there is no need to deal with old versions of the pieces. Only the external interfaces are frozen and versioned. This is similar to the Linux kernel. The user space API is frozen, but when an internal device driver interface changes all of the drivers in the kernel tree get updated in lock step. Doing it this way removes a lot of overhead in maintaining binary compatibility.
-- Jon Smirl jonsmirl@gmail.com -- VGER BF report: U 0.502564