Re: Where do you want to go tomorrow?
Hrvoje Niksic <hniksic(a)srce.hr> writes:
SL Baur <steve(a)vmailer.xemacs.org> writes:
> One possible way is to split the development trees such that we have
> a rigidly controlled stable branch (21.x) and a no-holds-barred
> development tree.
I am not sure what you mean by this. I would prefer to see
"semi-stable" releases followed by fully stable releases. Example:
21.1 == bugfix of 21.0; however, 21.2 == 21.1 + portable dumper + ...
At some point in the near future, we're going to branch the CVS tree.
The question is, what to name the new branch?
The tree we're working on now is a proper descendent of XEmacs 20.2
and not 20.3 or 20.4. It has at times been called 20.3-beta, 20.4-beta
and 20.5-beta before we decided to bump the major version number. The
multiple version number changes break any kind of automated tool that
maps a version number to CVS tag.
I'm also not very happy with the way tagged "beta" versions are
handled. Conceptually it would be neater to strictly use numbers
only.
This doesn't mean that 21.2 has to be totally unstable, or
no-holds-barred.
It probably won't be totally unstable. There's a certain loss of
flexibility about when unstable patches can be accepted though. It
would be nice to have a no-holds-barred development tree that we don't
have to worry about releasing for a year, but still maintain the
option of putting out more frequent releases. As anyone who has
navigated the CVS tree knows, we do not have either 20.3 or 20.4 in
CVS and I'd kind of like to close that loophole for the future.