[development] Site specific modules

Michael Prasuhn mike at mikeyp.net
Wed Apr 28 15:53:37 UTC 2010

Use git-svn and then you have got branches (which areuch easier to  
merge than svn branches) and you also get git add interactive and hit  
stash as well.

Sent from my iPhone.

On Apr 28, 2010, at 7:42 AM, nan wich <nan_wich at bellsouth.net> wrote:

> At my current location, I have developed a major site-specific  
> module (well over 100K). I have already split the admin, pages, and  
> blocks out into separate files. I have largely done this on the same  
> model as I use for my DO contribs.
> At any given time I may have four or five changes in place at  
> various stages of testing, and working on the next change. The  
> problem is that the powers-that-be occasionally want one change  
> moved to production quickly. I can't do that without potentially  
> moving untested changes too.
> So I'm looking for ways that others get around this situation.  
> Certainly I can move various smaller pieces into include files; this  
> is not a major problem as we use eAccelerator to cache all the  
> modules any way. Is that the best way or only way? We do have SVN  
> available.
> Nancy E. Wichmann, PMP
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin  
> L. King, Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100428/bd1ba688/attachment.html 

More information about the development mailing list