Re: [Evolution-hackers] bug fixing in stable 2.22.x branch

[Srinivasa Ragavan <sragavan novell com>]

Patrick

Evolution follows GNOME release cycles, which has just three dot
releases on the stable branch (2.22.3). And after that only for
DoS/Vulnerability fixes there will be dot releases. Distros shipping
2.22.x will pick patches from trunk/2.22.x and apply as and when
required. (Atleast for OpenSUSE, I/my team does that). Im sure
Ubuntu/Fedora too does the same. 

If it is a really issue, may be mailing the distributors list on picking
some patches for Evo/Eds may help.

-Srini.
 
On Tue, 2008-08-19 at 18:41 +0200, Patrick Ohly wrote:
> Hello,
> 
> I have a question primarily to the maintainers of the various Linux
> distributions which include Evolution 2.22.x (Ubuntu 8.04 LTS, Debian
> Lenny), but also to the Evolution hackers: the latest stable release,
> 2.22.3.1, still contains bugs. There are different ways to deal with
> this:
>      1. Evolution upstream continues to apply bug fixes to the 2.22.x as
>         long as important distributions use that.
>      2. Maintainers of packages apply patches locally, without or with
>         help by Evolution upstream. Upstream could help with bug
>         tracking.
> 
> What's the current practice? It seems that upstream has already stopped
> updating the 2.22 branch and bug fixes are only applied to trunk [1].
> 
> I'm bringing this up because at least one of the bugs will become
> critical in September: as noted this week [2], the conversion of system
> time zone information into libical time zone information (as used by
> Evolution) yields an end of summer time which is one week too early for
> Western Europe. It might also be incorrect for other countries and for
> the beginning of summer time.
> 
> That's particularly disappointing because the work on improving time
> zone support [2] was supposed to solve such issues. Now it looks like
> Evolution will fail to display events at the right time - once again!
> 
> In addition to this problem I'm sure there are other bugs which could be
> included in another 2.22.x release. The broken Exchange Connector
> contact change tracking [1] is one example.
> 
> [1] http://bugzilla.gnome.org/show_bug.cgi?id=546934#c2
> [2] http://bugzilla.gnome.org/show_bug.cgi?id=548268
> [3] http://www.estamos.de/blog/2008/06/22/time-zone-handling-in-evolution/
>