#721535 evolution: Please don't ask submitter to report bug upstream

Package:
evolution
Source:
evolution
Description:
groupware suite with mail client and organizer
Submitter:
Ross Boylan
Date:
2013-09-01 18:12:05 UTC
Severity:
normal
#721535#5
Date:
2013-09-01 18:08:56 UTC
From:
To:
Dear Maintainer,

Your reportbug template asks that bugs be submitted directly upstream on the
grounds of being understaffed.

There are a number of problems with that; I'm filing this bug because upstream
is not supporting the version in wheezy.

I interpreted the instructions to mean "submit anything that is not obviously a
packaging issue to upstream."  Another problem is that an end user, such as
myself, encountering a problem, can only speculate about whether the issue is
present in the upstream code, or is Debian-specific.

Finally, isn't policy that all bugs should go to debian and the maintainers
submit upstream only if appropriate?

I just submitted a bug upstream, which produced this response in minutes (the
reportbug gui seems to have mangled it a bit):
https://bugzilla.gnome.org/show_bug.cgiid=707235
  Evolution | Mailer | 3.4.x

Matthew Barnes <mbarnes> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |mbarnes@redhat.com
         Resolution|                            |OBSOLETE
--- Comment #1 from Matthew Barnes <mbarnes@redhat.com> 2013-09-01 17:53:12 UTC
---
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore.
GNOME developers are no longer working on that version, so unfortunately there
will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new
functionality. You may need to upgrade your Linux distribution to obtain a
newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer
version of GNOME.