[Fwd: [Gimp-print-devel] RELEASE ANNOUNCEMENT: Gutenprint 5.0.0-rc3]

[Daniel Robitaille]

On 5/19/06, Ondrej Sury <ondrej at sury.org> wrote:
> Hi all,
>
> is there a slight chance to get this updated gutenprint driver to
> dapper?  It seems to incorporate many important changes, but I
> understand that this is pro and cons together given that we are so close
> to release.
>
>> MAJOR CHANGES BETWEEN GUTENPRINT 5.0.0 RELEASE CANDIDATE 2 AND
>>   GUTENPRINT 5.0.0 RELEASE CANDIDATE 3:
>>
>>   22) The Lexmark driver should now print correctly (this is only
>>     partially tested).
>>
>> The following bugs have been fixed since Gutenprint 5.0.0-rc3:
>>
>> 1458059 Lexmark Z52 not working

http://sourceforge.net/tracker/index.php?func=detail&aid=1458059&group_id=1537&atid=101537


This bug is also present with the Lexmark z53 in Dapper, a regression
from all previous Ubuntu version:
https://launchpad.net/distros/ubuntu/+source/gutenprint/+bug/6627

It seems it is not even solved in rc3, but only in a more recent CVS
version  if I understand the wording of their announcement.

Currently that bug is the only reason why I will not upgrade our
family home PC to Dapper; Being able to print is somewhat essentially
with young kids :)

By now, due to a the timing of this bug finally being solved upstream,
 I have resigned myself that at one point after the Dapper release I
would need to figure out a way around this problem, by using Breezy's
gimprint in Dapper, or building dapper packages of the newer available
version post-rc3  of gutenprint.


Which lead me to question:   what's the best way to warn users of a
regression like this before  an upgrade?  If I was Joe User and would
upgrade my Ubuntu computer only to find afterward that the printer
doesn't work due to a bug first reported months ago in Malone, I would
be annoyed.

Should a list of known regressions, possibly as part of the Release
and Upgrades Notes (which traditionally I think only appears on the
website/wiki)  could be located along side other help documents on the
LiveCD initial boot menu or as a desktop link beside the current
Examples folder?  It doesn't mean it would be read by the users about
to upgrade, but the chances of this would be a lot better, and it
would make the Upgrade/Release notes a lot more useful than only
having them on the web site.

Daniel

-- 
Daniel Robitaille