Bug 621517 - Welcome email messages have wrong links
Summary: Welcome email messages have wrong links
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-05 10:45 UTC by Matthew Barnes
Modified: 2010-11-10 20:22 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-10 20:22:29 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 626059 None None None Never

Description Matthew Barnes 2010-08-05 10:45:18 UTC
It was pointed out to me in an upstream bug [1] that Evolution's welcome email that you see on a fresh install has all kinds of incorrect or obsolete links, including our project website, bug tracking website, mailing list subscription page, and FAQ.  Some of those links point to novell.com when they should point to gnome.org.

I fixed this for all the various translated welcome messages, and I would like to backport the commit for RHEL 6.0.

http://git.gnome.org/browse/evolution/commit/?id=0169ef37928b3190aec8c4acb2045c9925d83f40

Requesting this as a blocker.  There are no code changes, I would just like for users' first impression of Evolution to not be chock of errors.

Comment 1 Matthew Barnes 2010-08-05 10:46:33 UTC
Whoops, upstream bug link:

[1] https://bugzilla.gnome.org/show_bug.cgi?id=626059

Comment 11 Tomas Pelka 2010-08-17 08:06:02 UTC
Links working as expected, moving to verified (evolution-2.28.3-10.el6).

Comment 12 releng-rhel@redhat.com 2010-11-10 20:22:29 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.