Modularization development notes
Kevin E Martin
kem at freedesktop.org
Sat Apr 16 07:51:55 PDT 2005
On Fri, Apr 15, 2005 at 10:13:51PM +0100, Sergey Udaltsov wrote:
> Hi
>
> > > Should we try to merge our xkb stuff with the one of the
> > > xkeyboard-config project?
> > >
> > > http://www.freedesktop.org/wiki/Software_2fXKeyboardConfig
> > >
> > > Or is this something we should target after the initial release 7.0,
> > > so we don't need to change the monolitihic tree that much? Don't know
> > > if the Ivan/Sergey are subscribed on this mailing list to discuss this
> > > ...
> >
> > As you mention above, we would need to integrate it into the monolithic
> > tree for the 6.9/7.0 release since the code is shared between the two
> > trees. If it is something that Ivan and Sergey feel is well tested and
> > is ready to be put into wide use, then we should consider it; otherwise,
> > it would probably be wise to wait until after the initial release.
> I am subscribed, as you may see:)
>
> I would say we are VERY interested in getting into 7.0 release. Our
> release 0.5 is the best we could do so far - without real massive
> testing which we can only get if xkeyboard-config is included into
> xorg (or excluded explicitly - so people would have to download our
> module separately). We have a LOT of keyboard-related bugs fixed (bugs
> reported against monolythic xorg tree) - so let's finally present
> these fixes to users.
Hi Sergey,
This sounds like it will make lots of people happy. The only part that
worries me is that you said above that it hasn't had massive testing.
But, I think it if it can be integrated into the monolithic tree very
soon, we should be able to get better testing before the simultaneous
6.9/7.0 release.
The reason for putting your code into the monolithic tree is that we are
sharing the same sources between the two trees for the 6.9/7.0 release,
so anything that is in the monolithic tree (where there isn't a separate
upstream project) will also be included in the modular tree. See the
"Transitioning from monolithic to modular" section of the modularization
proposal for details on why we're doing this and how it will happen.
So, the first step in getting your code included in this initial modular
release is to integrate your changes into the monolithic tree. After
this first release, we will open the modular tree up to new code that is
not also in the monolithic tree.
Thanks,
Kevin
More information about the xorg-modular
mailing list