On Tue, Oct 25, 2016 at 01:08:21AM +0100, Dominik Vogt wrote: > On Tue, Oct 25, 2016 at 12:53:44AM +0100, Thomas Adam wrote: > > On Tue, Oct 25, 2016 at 12:48:01AM +0100, Dominik Vogt wrote: > > > Okay, then how about this: > > > > > > 1. Start a branch fvwm2-stable at 2.6.6 and document it as the > > > long term stable branch. > > > > OK. > > > > > 2. Backport fixes and functional changes from master. > > > > OK. (Which, and why?) > > Obviously at least the fix I've just made to FEvent.c as it was > introduced in 2.6.6 and breaks things really badly. The fix for > the hang in FvwmButtons is another likely candidate. There are > only a few interesting commits. Possibly the things you mentioned > in NEWS, which sound all like small changes. > > > > 3. Release 2.6.7 on this branch with a proper announcement. > > > > OK. > > > > > 4. Release 2.9.0* on master and announce it as the release > > > starting future development towards fvwm3. > > > > I wouldn't bother with this point---fvwm3 should be a separate repository > > entirely. > > Why? Unless some people step up and tell us they'd want to take > over fvwm2 development, what is the gain of duplicating all > infrastructure? > > Well, at the moment the only interesting issue is how to name the > release tags. I'd prefer a naming scheme like 3.-1.x, but the > tools will probably not like this. :-) > > > > I can take care of 1 and 2 but need some help with 3 because I've > > > never done a release using the new infrastructure. > > > > I can take care of that if you like? > > That would be good (I'm assuming that you mean just #3). Give me > some time to organise the fvwm2-stable branch (suggestions for a > better name welcome maybe "stable-fvwm2").
The branch dv/stable-fvwm2 is up for review. Collecting the patches was a piece of cake. Just one conflict with the NEWS file. The branch builds fine for me, without warnings, and I'm using it now for work. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
