Time for the release of Gnus 5.10.3?

Time for the release of Gnus 5.10.3?

[Reiner Steib]

Hi,

in a German newsgroup people noticed that some versions of Gnus (Gnus
5.10.2 and early CVS versions after the release of 5.10.2) have a bug
in the RFC2047 header encoding that leads to additional spaces[1]:

"Subject: Re: Altes ..." (original subject)
"Subject: Re: \n =?iso-8859-1?q?Altes_..."
             ^  ^  (Buggy encoding/folding w/ Gnus 5.10.2.)
"Subject: Re:  Altes_..."
             ^^ (unfolding --> two SPC chars!)

IMHO, Subject corruption is serious bug, because it destroys threading
in some clients.  As this and other related problems have already be
fixed in current CVS[2], I'd suggest to release Gnus 5.10.3 soon (and
encourage people to upgrade).  Announcing an imminent release a couple
of days before would be nice, to give us the change to commit pending
(doc-) fixes in time.

Bye, Reiner.

[1]
,----
| ELISP> (load "/usr/local/share/emacs/site-lisp/gnus-5.10.2/rfc2047.el")
| t
| ELISP> (with-temp-buffer
| 	 (insert "Subject: Re: Altes MTB aufrüsten oder neues Biligrad kaufen?")
| 	 (rfc2047-encode-message-header)
| 	 (buffer-string))
| "Subject: Re: \n =?iso-8859-1?q?Altes_MTB_aufr=FCsten_oder_neues_Biligrad_kaufen=3F?="
`----

[2] See Changes by Dave Love.  Current Gnus CVS gives (correct):

"Subject: Re: Altes MTB =?iso-8859-1?q?aufr=FCsten?= oder neues Biligrad kaufen?"
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

Re: Time for the release of Gnus 5.10.3?

[Romain FRANCOISE]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> I'd suggest to release Gnus 5.10.3 soon (and encourage people to
> upgrade).

And maybe we could start No Gnus right after that?  Patches for new
features have been piling up since the freeze...

-- 
Romain FRANCOISE <romain@orebokech.com> | Shine the headlight, straight
it's a miracle -- http://orebokech.com/ | into my eyes.

Re: Time for the release of Gnus 5.10.3?

[Xavier Maillard]

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

>  Hi,
>  
>  in a German newsgroup people noticed that some versions of Gnus (Gnus
>  5.10.2 and early CVS versions after the release of 5.10.2) have a bug
>  in the RFC2047 header encoding that leads to additional spaces[1]:
>  
>  "Subject: Re: Altes ..." (original subject)
>  "Subject: Re: \n =?iso-8859-1?q?Altes_..."
>  ^  ^  (Buggy encoding/folding w/ Gnus 5.10.2.)
>  "Subject: Re:  Altes_..."
>  ^^ (unfolding --> two SPC chars!)
>  
>  IMHO, Subject corruption is serious bug, because it destroys

Clearly yes it is.

>  threading in some clients.  As this and other related problems have
>  already be fixed in current CVS[2], I'd suggest to release Gnus
>  5.10.3 soon (and encourage people to upgrade).  Announcing an

Yep. When will the No Gnus development begin too ?

zeDek
-- 
"Wirf den Stein als erster, sonst nennt man dich einen Epigonen" (Lec)


[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

Re: Time for the release of Gnus 5.10.3?

[Thomas Hühn]

On Sat, 16 Aug 2003 12:53:40 +0200, Reiner Steib wrote:

> in a German newsgroup people noticed that some versions of Gnus (Gnus
> 5.10.2 and early CVS versions after the release of 5.10.2) have a bug
> in the RFC2047 header encoding that leads to additional spaces[1]:

Yes, that's not good. At the moment I usually use CVS Gnus. But I'm going
to use the latest release; at least as soon as No Gnus is started.

Is it feasible to load CVS Gnus' rfc2047.el or are there any dependencies
on other CVS stuff, which might break things I'm not aware of?

Alternatively, a 5.10.3 release would be really nice.

Thomas