On Mon, Oct 24, 2016 at 11:24:58PM +0100, Dominik Vogt wrote: > How about a compromise: Leave the code in, but announce that > these features are deprecated and will not be maintained anymore. > So, if any people still use some of them (FvwmTheme, FvwmWinList, > FvwmTaskBar and GNOME support being the most liekely), they can > still use the code as it is. If any problems arise with these > features, all we'll do is providing information on replacing the > features.
That's OK. I'm done with it anyway; I've put a lot of effort into dragging FVWM out from its hiding place; improving it in the best way I could. I'm actually proud to leave it in the state that's in in now---in the last six months of effort I've spent putting into this, I've yet to have anyone tell me that they'd miss these things, or that they're actually used. But maybe you know different, in which case you're more than free to go ahead with this---but know that I find it rather insulting to think that my efforts have been largely ignored on the idea that the small minority of users might be inconvenienced by these changes. I just don't think that's true at all. Trying to rearrange things is madness---and I won't have master rebased because of that. That's not how this works, and I'm not hearing a good reason for this at all. If we're leaving 2.6 behind, we should do that by releasing master as 2.6.7 and calling it a day. If people want something so badly, then they can use 2.6.6 and do whatever ontop of it. It's not as if this sort of thing hasn't been done in the past (fvwm95). Kindly, Thomas
