2.6.0 tag is set on...

[Inge Wallin]

On Monday, February 04, 2013 10:00:05 Cyrille Berger wrote:
> The conclusion on IRC was to reenable it for 2.6.1 (in two weeks).

That sucks badly for Calligra Author since the only thing that we can actually 
say that we bring to the table is ebook export.

The filter was arbitrarily disabled due to a crash, then *not* reenabled when 
the crash was fixed. The disabling was done by people who are not involved in 
Author and I'm pretty sure the same is true for the IRC discussion.

What I am - actually - a little bitter about is that the filter was just 
disabled without any discussion with me the very day before the tagging. And 
now the IRC discussion, also without me, came to the conclusion that it's not 
so important and that it can just wait two weeks. If you ask me, it can't wait 
two weeks because half of the reason for Author 2.6 has just disappeared.

Can we please reconsider this?

	-Inge


> 
> On 2013-02-03 22:40, Inge Wallin wrote:
> > On Sunday, February 03, 2013 12:32:36 Cyrille Berger Skott wrote:
> >> 97fec182466ace56fd7fb71fdb113b1f88271b8f
> >> 
> >> 
> >> http://quickgit.kde.org/?p=calligra.git&a=commit&h=97fec182466ace56fd7fb
> >> 71f db113b1f88271b8f
> > 
> > Could we please reset it to 5d8d95ae6dd29e1d03718e7b9579b78e80fdb78c?
> > If not,
> > Calligra Author will not have the export filter for mobi ebook which
> > was
> > disabled due to a crash the day before the tagging. The crash only
> > occurred on
> > 64 bit systems and was fixed on the same night but the filter was
> > never
> > reenabled.
> > 
> > I have now backported the fix to 2.6 and reenabled the filter. The
> > reenabling
> > commit is the one with the SHA hash above.