Re: FVWM: FVWM3-1.0.0 is released

Thomas, As an end user, rather than developer, I would agree with
Dominik on this request.  I think of Firefox which has gone through many
upgrades, but it has always been Firefox, even when breakage for
upgrading occurred.  Also KDE and XFWM have had upgrades that involved
breakage unless special steps were take. The upgrade process was
clearly explained and warned. I currently have both fvwm-2x and fvwm-3x
installed side by side and there is no issue. fvwm-2 is the package
maintainers version, fvwm-3 is the pre-release version  I installed.
There was great confusion when moving from fvwm-1 to fvwm2-x and I
experienced a lot of confusion through the whole time as fvwm2 went
back to using fvwm file locations and new config file.  In you own
words, there isn't any breakage at this point, and it will be
introduced at a later time. Please just make it fvwm-3.0.x and when
breakage is introduced change it to fvwm-3.1.x.
Cheers, BrianA_MN
------------------------------------------------------------------------------------------------------------------
On Thu, 3 Sep 2020 13:44:10 +0100 Dominik Vogt <[email protected]>
wrote:

> On Thu, Sep 03, 2020 at 01:27:19PM +0100, Thomas Adam wrote:
> > It's a tricky one.  Right now, things have not diverged because I
> > haven't implemented those changes.  I'd always viewed Fvwm3 as
> > being a departure from Fvwm2 -- and hence any association with it
> > at the moment as being equivalent is just because it's lacking any
> > breaking changes.  It's also an easier transition for any one
> > wishing to try Fvwm3 who's previously used Fvwm2.
> >
> > That's one of the reasons why I went with version 1.0.0 -- Fvwm3 is
> > going to be separate from Fvwm2 over time, in that I'm not
> > expecting to maintain compatibility, and I wouldn't therefore want
> > to mislead users with a false version number.
> >
> > There may well be some overlap with Fvwm2 in terms of unchanged
> > file names (fvwm-config springs to mind), although I think for the
> > most part Fvwm2 and Fvwm3 can co-exist.  I'll try and make the
> > distinction better in future releases, so that it's easier for
> > package maintainers to allow Fvwm2 and Fvwm3 to coexist.  
> 
> The exact same reasoning led to the "fvwm2" project, and it caused
> a whole lot of useless work to eventually clean up and rename it
> to fvwm again.  The autotools can take care of having two versions
> installed in parallel (--program-suffix configure option).
> Distributors know how to use these options.
> 
> And as far as I understand, nobody is going to maintain the 2.x
> version anyway.
> 
> Ciao
> 
> Dominik ^_^  ^_^
> 
> --
> 
> Dominik Vogt
>