New answers tagged

1

It sounds like you're missing branches (or rather 'tags' or 'release' branches). Instead of using your SVN revnum as a reference to determine which version you're installing, you should create a branch at that released revision. You then deploy that branch name. It makes it easier to branch even if there are no changes so every module keeps the same ...


1

I think you have a lot of good ideas already, I've used most of them on various projects throughout the years, and your primary concern seem to be the inability to tell what version of all modules where included in a given package if you split them up. I'm all for splitting them up, at some level of granularity, especially if you have multiple teams and ...


1

Don't think too much about Pip. If your Setuptools configuration works correctly, it's easy enough to upload all and only those files you actually want to PyPI (at which point end users will be able to install it with Pip; developers will be cloning your git repository since they need history for things like git bisect to work, and Pip does not provide git ...


1

I'm not necessarily saying you shouldn't host your company's repository in the cloud, but I've personally experienced some disadvantages and pain with cloud hosting. How fast and reliable is your internet connection? To me, that is the single biggest consideration. For example, my company is located in a pretty rural area. While our intra-net speeds are ...


0

You group commits in branches: each branch is a set of commits. When you merge commits, you are putting one set of commits inside another branch, effectively building a hierarchy of commits: main branch, features, bugs, experiments, you name it. Ideally, your main branch is a succession of merge commits. If you only look at first-parents (git commands ...


0

I had the same issue thinking about this until I discovered that Git numbers its parent branches. Given this, the usually annoying merge commits that are generated can be considered summary nodes. And all extra details can be banished from view, leaving a single, summarized linear history. Check this blog post for details and examples.


6

The idea of HEAD is that every time a developer starts a task, they start with HEAD, and when they are finished they merge back into HEAD. That way you always know where to find the latest version of the code. You are doing something different. It sounds like each programmer begins by selecting a somewhat arbitrary tag from the existing tags and starts ...



Top 50 recent answers are included