cvs

git has replaced cvs as the version control system for drupal. -

There is a number of articles on to how handle git
but they don't really address the needs of site maintainers.
I am aware that this is a developers' group but since I found no better place to turn to...
... let me git it a try, anyway.

I have found no article specifically dealing with the needs of drupal admins
when having to MOVE FROM CVS TO GIT ON PRODUCTIVE SITES.

Let me ask a couple of questions as a site admin on Linux systems
on what to do in order to successfully move to git.

--> Actually I am going to tell you how I used to do things via cvs
hoping to get hands-on tips on how to do them via git.

I have an idea for dealing with duplicate modules at a more (but not fully) automatic level.

As I understand the problem duplicates are caused by one of the following situations:

Hi, i have just committed the 6.x release for the galician language, and the packaging script has thrown the error:
"[...] msgid' andmsgstr' entries do not both end with '\n'" (weird problem btw...)

Anyway, I've corrected the error and committed the changes, so my question is... does the script recognize the changes, do I have to re-tag the release, or create a new version...? What do I have to do now for the packager to show the right release?

Also, does the script throw all errors, or it just stops on the first one?

Thanks!

I just thought I post a little information about a presentation I am going to be giving at the October meetup. At the last meetup, I was asked if I would mind giving a presentation on the use of GitHub in managing Drupal projects. We have pretty much switched all of our development versioning to Git at CollectiveColors.com, because it has shown to have significant benefits in our own development processes.

Git makes it easier for us because:

1. It allows us to better collaboratively develop our software while minimizing the impact of code conflicts.
2. Allows us to easily track what we have developed.
3. Branching and merging of repositories is a breeze.
4. It is very easy to turn any directory tree into a Git repository.
5. Git submodules are perfect for Drupal development.

We have learned a lot of really cool methods for managing software projects using Git and GitHub, so we figured that we would share some of what we have learned in our journey so far. Although, I have a rough outline of what I want to talk about during this presentation, I am open to hearing your suggestions, after all I'm not presenting to myself.

So what I am thinking so far? ...

Kevin and crew--

At OMPCamp in Portland we started (but did not conclude) a discussion about running / installing Drupal from the CVS repositories. I was under the impression that installing Drupal from CVS made updating and patching the system significantly easier. My takeaway on the conversation was that it wasn't as great an idea as I'd been led to believe.

Can you share your thoughts more completely on this idea? Is there a price to be paid for that convenience? Is it okay for other systems, just not OMP? Did I totally misread the (brief) discussion?

Thanks!

I am in the early stages of developing a group of modules that will be inter-dependent and will ship as a single downloadable project. This has got me thinking about avoiding module namespace conflicts for submodules that ship as part of other module packages.

Si todavía no se han enterado, Marco Villegas (@marvil07) está participando en Google Summer of Code 2009 (GSOC), vean el anuncio oficial y en su blog.
Y hoy acaban de aprobar la cuenta CVS de Franco Cedillo (@AdagioParaCuerdas), eso significa que ya tenemos maintainer para el release D6 del módulo Dokeos.

As a student representing my college, I am organizing an online quiz on open source for a group of five colleges on 18 April 2009 which has more than 100 questions. I was lazy to upload question manually one by one so i wrote a quiz_questions_import script based on this article http://acquia.com/blog/migrating-drupal-way-part-i-creating-node. Bulk question import is a something often often asked feature in quiz issue queue so like to share this script with you guys here.

quiz_questions_import.php


<?php
require 'includes/bootstrap.inc';

Hey there fellow Drupaleros,

I'm seeking peer review of my video about my CVS/SVN workflow regarding deployment for a multisite setup. I'd learned about vendor branching and svn:externals a few months ago and finally got around to setting up a system I was happy with.

What I'm wondering is if I could do anything better or how other people are doing similar things, but slightly different.

All feedback is welcome, leave comments on the site or email me via gdo.

When I gained cvs access, I read the drupal book pages on cvs and also merlinofchaos blog, and polled irc drupal-support.

What I came up with was that there are 2 ways of maintaining releases for contributed modules.

1) Always have the latest code in head, and only release a branch when the new version of drupal comes out. For example when working with module and it is for drupal5 the code is found under HEAD, when the module is upgraded for drupal6, create a branch DRUPAL-5 for the drupal5 module.