2-Version software: Best VCS approach?
Posted
by Tom R
on Stack Overflow
See other posts from Stack Overflow
or by Tom R
Published on 2010-03-02T18:10:00Z
Indexed on
2010/03/29
4:53 UTC
Read the original article
Hit count: 309
I suppose I'd better explain my situation:
I'm in the process of developing some software, and I'm at the stage where I'd like to split my project into two branches which differ in features. It so happens that this application is an Android application which I will be deploying on the Market, which has the constraint that every app must have a unique package identifier (sensible, no?).
My current approach has been to clone the git repo of my original project, but this causes issues with package names. I want the system to be robust enough so that a bugfix/new feature on one branch will merge into another branch, but only when I want it to.
Does anyone have any suggestions?
© Stack Overflow or respective owner