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?) > 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. > 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? -- Thomas Adam
