Bug in cperl-mode.el - unexpanded CVS keyword
acs at alumni.princeton.edu
Thu Dec 22 23:16:55 EST 2011
Dear Stephen et al,
On Thu, Dec 22, 2011 at 10:52 PM, Stephen J. Turnbull wrote:
> Certainly it would be good for our image and our own morale if both
> packages and core (mea maxima culpa) got on to regular release
> schedules, but I don't see the benefit from a one-off effort to
> re-release right now?
Look at it this way: since the move to Mercurial, the package code has
been checked and compiled, but not (beta) tested by our user base.
How many people actually build the packages? 2, 3, 4, 5? And then
how many packages do those of us all use? Not very many. The only
way to up the code coverage is to get those packages tested by the
user base. At this point it's clear that the packages were modified
by moving them to Mercurial. Is the expansion of the $Revision$
keyword the last issue we're going to find? Maybe, but we'll never
know until we start to get the packages tested.
The base code is a somewhat separate matter, but we have had a 21.5
release since the move to Mercurial, just not a 21.4 release. That's
one of the reasons I'm motivated to get a 21.4 release out.
More information about the XEmacs-Beta