2 Apr
2014
2 Apr
'14
3:35 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
I can disable the compton-tde build if required (it's a one-line patch),
this is not a problem. However, bear in mind that I did the because I
don't want to release kompmgr with R14 due to its myriad user-visible
problems. As a result, we would have *no* TDE-compatible compositor
officially available if compton-tde is disabled, forcing users to either
use kwin instead of twin or compile kompmgr/compton-tde manually if they
want compositing. I personally see this kind of thing as something the
distro maintainers would likely override (with a small distro-specific
patch) for a better user experience regardless of what we choose.
Remember as well that kompmgr always was alpha-level software, and that by
switching to compton-tde we are keeping feature parity but gaining
stability (I personally would rate compton-tde as beta quality with the
possibility to go to stable class in the release after R14).
To avoid any long discussions, how about the main dev team (myself,
Darrell, Slavek, and you) simply cast votes on this one-time override?
My vote: switch to compton-tde as the official compositor, but do not
disable or delete the kompmgr sources until the next release after R14.
Tim
More
importantly, I thought we were in a feature freeze.
Darrell
I would like to avoid one of those big discussions that sometimes get
started, but I fully agree with Darrell.
We set a freeze state to focus on the finalization of the 14.0.0 release,
trying to avoid last minute major changes.
The point is to avoid repeating the same pattern followed last year, where
freeze state was declared in July and then renames, changes, additions
.... were applied, basically resulting in a cancellation of the freeze
state.
Cheers
Michele -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlM7hZYACgkQLaxZSoRZrGG+iQDeLA/8yCq7x7dr2zm3Vf3lzLUC
UeZO5Nql6wooDgDeLkK0XybI3/tTODtjDK8+0kv7+Pas9/P3nlEb4Q==
=Pps8
-----END PGP SIGNATURE-----