[Freeassociation-devel] Default value for ical_errors_are_fatal

[Suman Manjunath]

Hello Will,

On Fri, Jan 2, 2009 at 17:05, Will Stephenson <wstephenson at kde.org> wrote:
> Speaking for the Novell KDE team, I request that we keep this switch set to
> fatal as late as possible in the development cycle, so that errors in apps'
> usage of libical are found instead of being masked.  Libical is complex
> enought that most errors are only found by having a broad range of test inputs
> from beta testers (several of the bugs in Kontact were only found in this
> way).  And bugs masked by enabling this switch will result in harder to debug
> apparent calendar corruptions and strange behaviour when talking to groupware
> servers, instead of obvious crashes.

Not only in the development cycle but also during the release,
post-release and maintenance cycles, you can __still__ always have
Kontact set to crash on calls to ical_error_* by setting the global
variable

 int ical_errors_are_fatal = 1 ;

in one of Kontact's initialization routines.

Likewise, the GNOME Evo team __will__ make sure that behavior is
consistent across distributions by setting the variable to 0 in one of
our initialization routines.

> Concrete requests for Novell packages (I'm talking to the Evo team here)
> * in openSUSE Factory, keep the switch off until RC (since we should have
> branched for SLE 11 already, it should stay off now)
> * for SLE 11, since it has a very long RC phase, keep the switch off for
> another month at least.

This is not the forum to decide what switch openSUSE/SLE should use.
Feel free to start a discussion opensuse-factory / SUSE devel mailing
lists about what you want to propose for the SUSE releases.

-Suman