TODO for 2.6.1
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. -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: TODO for 2.6.1
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. :) Kindly, -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: TODO for 2.6.1
On Sat, Apr 16, 2011 at 10:19:53AM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org 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. Exactly the same as you did below. I just tried following the directions: home cvs -d :pserver:d...@cvs.fvwm.org:/home/cvs/fvwm co -r branch-2_6_0 fvwm cvs [checkout aborted]: no such tag branch-2_6_0 home cvs -d :pserver:d...@cvs.fvwm.org:/home/cvs/fvwm co -r branch-2_6_1 fvwm cvs [checkout aborted]: no such tag branch-2_6_1 Neither of which worked. Yes, I know. It was only then I realised that nowhere in the docs/DEVELOPERS file does it mention: Create a new branch which is 'stable'. To work on 2.6.x we need a branch. Yes, and I'm assuming I can do this based on a checkout of files tagged at version-2_6_0? The point is, my knowledge of CVS branching is not too good, and I don't necessarily know *how* to do that, if it's possible, or if I'd end up breaking things. That's part of the problem with CVS; nothing is sand-boxed, and anything I do is always acting on the central server. :) I'm glad to see you working on 2.6.1. It's needed, unfortunately. But I can't do it until I understand the above points. I could just go away and read the docs, but I'd only get one shot of doing it, and I'd rather someone who is more familiar with CVS branching, and who has done it in the past can just verify with me exactly what I need to do. As it currently stands I have two CVS checkouts of FVWM: * One which reflects the version-2_6_0 tagged files. * One which reflects the version-2_7_0 tagged files. But neither of these are branches, obviously. So I'm wondering if I've just shot myself and the rest of the dev team by not realising this sooner. I hope not. 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. Indeed. 2.6.X was always a means to an end, and I already have an email proposal outlined for $THE_FUTURE, but there's some serious housekeeping needed doing first; sorry about that. TIA, -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: TODO for 2.6.1
Thomas Adam tho...@fvwm.org writes: On Sat, Apr 16, 2011 at 11:18:16AM -0400, des...@verizon.net wrote: Creating a branch is much further down the page. I see that now I'm reading two different files, thanks. I've issued the right command, but now all I get is spurious messages: [n6tadam@debian][fvwm-2.6.0][fvwm]% cvs rtag -b -r version-2_6_0 branch-2_6 . cvs rtag: [15:32:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:32:36] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:33:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:33:36] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:34:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice I do not know how long such a command as issued should take, or whether the above output about locking is preventing the command from running, but so far it's been ten minutes, with the same message above being printed out periodically. Something for Jason to investigate? I seem to recall having similar locking problems before when I tried creating a CVS branch in FVWM's repository. Yep, according to this page: http://tinyurl.com/ytdv54 something didn't complete in fvwm-web. Maybe that's why I couldn't find the pictures you uploaded. Looks like we do need help on the server.
Re: TODO for 2.6.1
[Cc'ed Jason on this -- Hi, Jason!] On Sat, Apr 16, 2011 at 11:45:51AM -0400, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: On Sat, Apr 16, 2011 at 11:18:16AM -0400, des...@verizon.net wrote: Creating a branch is much further down the page. I see that now I'm reading two different files, thanks. I've issued the right command, but now all I get is spurious messages: [n6tadam@debian][fvwm-2.6.0][fvwm]% cvs rtag -b -r version-2_6_0 branch-2_6 . cvs rtag: [15:32:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:32:36] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:33:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:33:36] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice cvs rtag: [15:34:06] waiting for cvs's lock in /home/cvs/fvwm/fvwm-web/pictures/decorations/window_deco_ice I do not know how long such a command as issued should take, or whether the above output about locking is preventing the command from running, but so far it's been ten minutes, with the same message above being printed out periodically. Something for Jason to investigate? I seem to recall having similar locking problems before when I tried creating a CVS branch in FVWM's repository. Yep, according to this page: http://tinyurl.com/ytdv54 something didn't complete in fvwm-web. Thanks, Dan. I wondered about that -- I've added in new screenshots before; but I did think something went wrong when I saw the blank commit messages come through on the mailing list. That said, the screenshots I added are there now -- I see them on fvwm.org anyway -- all the ones from Christine. Those were the only ones I added. Maybe that's why I couldn't find the pictures you uploaded. Looks like we do need help on the server. Jason -- any ideas as to the above output? When I was committing to both fvwm and fvwm-web I had no errors from either repository that something had gone amiss. Does CVS report such problems usually? I'm just more interested generally in how these sorts of things arise, and how they're kept track of. Oh well -- I'll hold off on 2.6.1 for now until the CVS issues can be fixed. Jason -- if you need anything, just ask. -- Thomas Adam It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: TODO for 2.6.1
On Sat, Apr 16, 2011 at 09:26:15PM +0200, Dominik Vogt wrote: On Sat, Apr 16, 2011 at 02:03:18PM -0500, Jason L Tibbitts III wrote: Did I mention how much I dislike CVS? We really need to have a discussion about moving to git. I'm all for git. CVS feels so *old* when you have gotten used to git. It was in my proposal email to do this. I already maintain a Git mirror: https://github.com/ThomasAdam/fvwm And unbeknownst to most people here have spent ages doing FVWM development from this repo, and exporting the commits to CVS. But yes, given I've already done the heavy lifting, I think this is a valid thing to propose, and I'll do so in a few days time, as there's still a lot of peripheral work to do in switching, etc. Please prod me though if I lag behind. :) -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
