Re: [Evolution-hackers] WebKit based Evolution composer status and future

[Patrick Ohly <patrick ohly gmx de>]

On Mon, 2014-03-17 at 09:25 +0100, Tomas Popela wrote:
> Regarding the future of WebKit based Evolution composer I'm proposing
> this: merge webkit-composer branch into master when the 3.12 release
> will be branched and continue to work on it in master branch. This will
> hopefully bring more testers for the new composer. When the code will be
> in master I will continue to develop it and also porting it to WebKit2
> with the rest of Evolution.

While I have no say in how Evolution gets developed, I nonetheless would
like to warn against merging unstable and known buggy code into master.
What if it turns out that the code can't be stabilized in time for the
next release? Can it be reverted or will Evolution have to go out with
known regressions?

I know that sometimes one has to take the bullet and release something
to get bug reports that one would not get otherwise. But IMHO that
should be the last resort when all other options of finding those bugs
have been exhausted. Just my 2 cents.

Bye, Patrick