Thomas Adam <[email protected]> writes: > On Sat, Apr 16, 2011 at 11:16:45AM +0100, Thomas Adam wrote: >> Hello all, >> >> Couple of interesting observations which we'll need to look at for 2.6.1 >> (which unfortunately might be sooner than I'd hoped): >> >> * I need to change the minimum Fribidi version to 0.19.2 due to all the >> deprecation warnings I found. >> * Need to add a suggestive note that XML::Parser is needed for >> fvwm-menu-desktop, and make it less chatty when this isn't the case. >> >> I'll be doing that now. Sorry. > > And so I have, but they're floating in my CVS checkout... > > Can someone with more clout than me regarding the CVS process for a stable > release take a look at the repository? The one thing I haven't done is to > create a branch to relect 2.6.0 -- at the moment it's just tagged. > > Should I create such a branch, from the tagged set of files at > version-2_6_0? That would then allow me to release a 2.6.1 I suppose. At > this point I'm just guessing. I guess these steps were missing from the > DEVELOPERS file. :) > > As soon as someone can clarify this, I'll get things rolling. Rather > embarrassing as I really had tested this on older installs. Hmm. At least > there's enough people taking an interest to point these things out though. > :)
Tell us what you did and the message you got. I just tried following the directions: home> cvs -d :pserver:[email protected]:/home/cvs/fvwm co -r branch-2_6_0 fvwm cvs [checkout aborted]: no such tag branch-2_6_0 home> cvs -d :pserver:[email protected]:/home/cvs/fvwm co -r branch-2_6_1 fvwm cvs [checkout aborted]: no such tag branch-2_6_1 Neither of which worked. To work on 2.6.x we need a branch. I'm glad to see you working on 2.6.1. I hope in the future we do nothing in the 2.7.x series. I'd like to not have any future multi-year delays.
