The coder project doesn't have a DRUPAL-5 branch in CVS. This prevents automatically including the module in a CVS-based test or development site. Extra, manual steps are required to pull this module into the site and, at least with CVSNT, it requires some file-path kludgery to keep the checkouts from interfering with each other.

Comments

douggreen’s picture

Why can't use just use HEAD? I do my checkouts on a Windows system using the cvs command line client and the HEAD branch.

I'm avoiding branching because maintaining multiple branches on a project that is under active development, is time consuming.

ewhipple’s picture

You can certainly continue with HEAD if that works better for you. I can definitely understand the desire. However, you might be surprised at how much it could benefit others if you're willing to put up with the extra effort.

First example: I learned the hard way not to do a bulk checkout of HEAD in the contributions repository. I tried it while setting up my test site, and I got what I wanted: all 219 DRUPAL-5 projects plus the untagged, 5.x compatible ones like Coder, and that was cool. The over a thousand abandoned or not-yet-ported projects that are of no use with 5.0 were less cool. Starting from scratch, I did a checkout on everything with a DRUPAL-5 branch, but I didn't get some things I really wanted, like Coder and DHTML Menu.

It took me a few hours to figure out how to add the unbranched projects so I could still use CVS to keep track of everything all together. It's only a small amount of extra work going forward, now that I know how to work it. Still, you (and I, once I get my project going) can save other users a lot of that heartburn in the future by taking care to coordinate with the rest of Drupal's contributors.

Believe me, I understand not wanting to complicate things on your end. I've only just started with CVS, and it's immediately become way cool and a major aggravation, both at once. But, it's very clear to me, as a customer of Coder and of all the two-hundred-odd other modules, how useful it would be if they were all on the same track with code management.

Second example: In the months leading up to the 5.0 release, I saw a lot of module-related confusion and inefficiency, among developers and users both. Given the purpose of this module you've produced, I imagine you noticed it too. I kept thinking about that as I worked on my test site, and on the code improvements I've tried to write. I was pretty aware already, but it really brought this to a sharp point for me: how important it is to take the long view when deciding what's worth the effort and what's not, in developing software.

That's why I was so hep on getting this module set up. In case it hasn't come across, let me mention that Coder is cool beans! It has serious potential to help improve Drupal and affect a bunch of folks, and I for one intend to use it for everything I can. If it weren't that good, I wouldn't have done the extra work, and I wouldn't have bothered you with this CVS thing. That's why I really hope you'll be persuaded to give it a try.

douggreen’s picture

Status: Active » Fixed

You talked me into it. I also think that the project is pretty stable now. I've branched for 4.7 and 5 and added tags for stable releases for each. Thanks!

douggreen’s picture

Status: Fixed » Closed (fixed)