change status to Fix released (see gnome-bugs)
** Changed in: evolution (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/723898
Title
** Changed in: evolution (Ubuntu)
Status: New => Triaged
** Changed in: evolution (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/
Closing natty task then, keeping floating task.
** Changed in: evolution (Ubuntu Natty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
https://bugs.launchpad.net/bugs/723898
Title
I agree with Martin, and really appreciate his proposition. But there is risk
to break something just before the final release by re-enabling it and
disabling it just before. It is not worth it.
So let it open and retarget for O
** Changed in: evolution (Ubuntu Natty)
Assignee: Canonical D
Hi Martin,
I will discuss with Jean-Baptiste and inform you of our decision. I also
don't want you spending any unnecessary time on it :)
On Thu, Feb 24, 2011 at 12:52 AM, Martin Pitt
wrote:
> Hello Patrick,
>
> this feature was removed upstream because it causes a lot of crashes and
> is unmain
Hello Patrick,
this feature was removed upstream because it causes a lot of crashes and
is unmaintained. I don't think we can spend the effort in the desktop
team to maintain it ourselves.
Would it help if we re-enabled the feature during the natty development
cycle and disable it for the final r
** Changed in: evolution
Status: Unknown => Fix Released
** Changed in: evolution
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
https://bugs.launchpad.net/bugs/723898
T
