> > > @Curtis Schofield: The customer is asking for more than just changes to > the CSS -- he wants different content and some additional views. And I > agree that this could become a nightmare -- I plan to maintain a bill of > materials, SKUs and ECOs for each variant of the app. That should help > some. > > that will help you recoup costs - it will not help you maintain and scale your codebase - you are going to create yourself a nightmare the direction you are heading.
I know it seems like Git can do this - but this is not what Git is for this is what software is for - skip to making new and original mistakes - don't make the obviously avoidable ones. - see the following. As far as running a biz around this : http://www.sei.cmu.edu/productlines/ As far as software patterns: Check out the work on 'feature flags' http://code.flickr.com/blog/2009/12/02/flipping-out/ http://napkin.highgroove.com/articles/2011/08/22/introducing-setler-for-feature-flags -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
