>>>> "Bill" == William M Perry
<wmperry(a)aventail.com> writes:
Bill> So, the wife is going out of town for a week and liam has school in the
Bill> afternoons, and I don't need much sleep. Soooo... I'm going to try and
get
Bill> XEmacs/GTK upgrade to the 21.2 source base by friday. This will hopefully
Bill> include all the fancy glyph stuff andy has done.
Bill> Any objections? This would land on the main 21.2 branch. I really think
Bill> GTK should be made the default on systems that support it, and that is how
Bill> the 21.1.12 patches work, but for the first set of patches you would be
Bill> required to do --with-gtk=yes (or --with-gnome=yes).
I think putting the gtk changes on the main branch directly is far too
aggressive.
I would like to see:
- Bill upgrades his branch to 21.2 (or creates a new branch for
xemacs-gtk-21.2).
- Bill `finishes' the xemacs-gtk work, including boring stuff like
documentation, NEWS, and maybe even some test cases. Maybe a web
page could explain WHY we are creating a gtk-xemacs. I for one am
not sure. Bill, get thee a sourceforge account so you can write
that web page.
- Bill advertises this branch as a new 21.2 candidate. Of course this
branch defaults to --with-gtk=no.
- People try to use the xemacs-gtk-21.2 branch for their default
XEmacs and pound on random keys for a few months.
- After a month or two or three, when people see stability and
coolness, we merge xemacs-gtk-21.2 onto the main branch.
- When everyone sees the goodness that is GTK, we consider making
--with-gtk (autodetected, of course) the default.
- There is nothing stopping Bill from incorporating changes from 21.2
occasionally into his branch. Of course, this requires discipline
regarding branch names and a good understanding of the merge process.
Actually, I would like to see this for all major changes, not just
GTK. We haven't done that in the past. I'm very happy that Bill is
using CVS branches, and I wish other big changes did the same.
Regarding the timing of the merge, I would hope that Ben's
Mule/Windows changes come at a distinct period of time from the gtk
merge onto the main branch. It is better if XEmacs is only digesting
one major source of changes at a time.
Martin