Recent changes to XKB files & reminder of commit rules

[Alan Coopersmith]

I've noticed a recent commit made changes to the XKB config files
in the Xorg monolith.   Unfortunately, this broke several of our
current commit rules, so I figured it was time for a reminder:

1) We are in feature freeze now.  No new features or incompatible
    changes are allowed without permission of one or more of the
    6.9/7.0 release managers (Adam Jackson, Kevin Martin, & myself).
    Permission has been granted for a few changes, most notably EXA
    support, but you should still ask first.

2) Changes to the monolith need to have corresponding entries added
    to the xc/ChangeLog file.   (This is always in effect, not just
    near releases.   A similar rule for the modular packages will
    eventually be added as well, but we've been a bit loose on that
    so far.)

3) Due to the modularization work in progress, where the modular
    trees are sharing source files with the monolith, if you add,
    remove or rename a file in the monolith you should either:
	- fix the modular tree symlink.sh & other files as
	  appropriate
     or
	- send mail to xorg-modular at lists.x.org to warn the people
	  working on it that they may need to do so (or file a bug
	  in the "modular build system" category in Xorg bugzilla)

This change broke the modular xkb-data builds because they were using
files that got removed and don't have additions for the new files.

(There's also "4) All commits should generate mail to xorg-commit list"
  which didn't happen here, but I think that's a bug for the fd.o CVS
  maintainers, not a fault of the committer.)

Please try to stick to these so we can get a quality set of monolith and
modular releases out in the next couple of months.

-- 
	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering