Steve Youngs writes:
> What is it? Well, in a nutshell, it is our Bible. It is our
> "Procedures & Policies Manual".
>
> Here's a really rough, in no specific order TOC...
[Snip] There is just one topic I'd like to comment on right now.
> Making Releases
What version number schema do we want? The XEmacs team resently
adopted the same as used in the Linux kernel and I presume we want to
keep it?
Assuming so...
I'd recommend forking (21.4) and change it to working code (21.5), and
release 21.6 asap, preferably no longer than 2-3 months after fork.
21.7 is then what we'll presumably release as 22 (with multithreads
(if possible) and other bells.
There is mostly marketing rationale behind this. I presume we want
users, a lot of them, and fast. We can achieve this partly by having
the highest version number and therefore appear the most advanced
version of emacs (and we will be!). Xft will help, a lot. I'm
presuming we can push this into the 21.6 release and with the promise
of multi-threads in 22, we can probably get lots of help, if not just
excitement.
We should also aim for KDE and Gnome integration, even if there is no
active work on it, we should advertise for developers ... or
something, for it.
I am personally willing to work on Qt ism ... but that'll probably be
mostly for the Qt Embedded system. I'll just see about the actual
KDE.
Ok, now I've digressed far enough from the PPM I think, so I'll stop
now.
[Snip]
Have fun,
Johann
|