C. Bergstr?m wrote:
> Alan Coopersmith wrote:
>> I'm also planning on proposing
>> a new "X Gate" Project to host a live clone of the master NV gate
>>
> Please correct me if I'm wrong, but don't you already publish all of
> your patches? As a consumer and user of fox-* gates I'm quite happy
> with patches + tarball. If you're planning to import all the code into
> a monolithic hg repo then I'd really really kindly ask you don't. Xorg
> went modular exactly to avoid this.
The X Gate proposed would have the same build style and code layout as
what you see today in our tarball releases and fox-gate. The differences
would be:
- unlike the code drop tarballs & imports from the Nevada gate to
the fox-gates, it would be updated live, without requiring manual
intervention. Right now tarballs are published and changes pushed to
the fox gates when I get around to it.
- it would be an exact clone of the Nevada gate, like the code drop tarballs,
but unlike the fox-gate, which contains additional changes from Belenix and
Martux/Martin's projects
- it would follow the same policies as the Nevada gate - no putback without
code review, (if needed) ARC review, RTI, etc.
Basically it's the next step in the open development process for the X
consolidation - catching us up to where ON is, by moving our master gate
internally from TeamWare to Mercurial and keeping a live read-only clone
of that on opensolaris.org. The step after that, making the external gate
the read-write master requires more tools work be done, much like ON, and
is being coordinated via the new Open Development project.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
