Re: That emacspeak problem...

* David Kastrup (2005-01-21) writes:

> Ralf Angeli <[email protected]> writes:
>
>> * David Kastrup (2005-01-21) writes:
>>
>>> Perhaps we should put a column "current issues" on our web page to
>>> keep people up to scratch concerning known incompatibilities?
>>
>> I'd rather release 11.55 soon.
>
> How soon?  We have not have much feedback yet.

Something between two and four weeks from now.  This should be long
enough to get feedback about most of the potential obvious bugs.

> Believe it or not, but going through the complete release process,
> even when release notes and manuals and version numbers and stuff
> have already been done by somebody else, rarely takes less than
> several hours.

Answering questions about bugs already fixed in CVS takes time, too.

>> This would also fix the problem with the compiler message.
>
> But to be honest: we have a history of problems, in particular with
> XEmacs.

With XEmacs we currently have a particularly bad situation.  11.53 is
no longer in pre-release but a regular package.  This might lead to
more reports about the overlays-at bug.  11.54 is in pre-release and
Uwe doesn't like to apply patches.

> The "we don't need to mention them, all will be fine with the
> next release" mantra is not too convincing in the long run.

Yes, I am getting your point.  I was thinking of using a bug tracker
which would not require us to maintain a list of bugs and remedies by
hand.  But first, we don't have one which is controllable by email and
second, for the users it would be more convenient if these things are
presented in a structured way at a single place.  This would be a
point for your suggestion for the web page.  Of course this will only
work if there are only a few issues.  And if we don't have workarounds
for those bugs we'd have to make a new release anyway.

By the way, do we have a workaround for the compiler message?  If it
happens with pre-compiled Elisp files only, maybe recompiling the
source files will help.  Could somebody seeing the compiler message
check this?  If the compiler is quiet then, we could mention this as a
workaround.

Anyway, if I find the time I'll probably follow your suggestion to put
current issues on the web page just to get some traffic off our
communication channels.  But that doesn't invalidate the time frame
for a bug-fix release I mentioned above.

-- 
Ralf