Tag Info

Hot answers tagged

22

Personally, I choose option 3: keep versioning information in VCS metadata, specifically, tags. Git makes it very easy to do so, because there is a command git describe, which can uniquely describe a commit based on a tag. Here's how it works: If the current commit is tagged, output the name of the tag. Otherwise, walk the history backwards until you find ...


7

SQL scripts are the right way to go: The information was originally created via a sql statements, most reliable repeat-ability would come from the same script Import/export can also get tricky if two devs are modifying the same table. It's hard to code review an export file. It's hard to debug an export file We have 5 database environments in our world: ...


7

Yes. It is good practice to keep most of the version number in vcs. If we consider semantic versioning semver.org where we have major.minor.patch.build the first three must live in vcs. The last one can be a incrementing number from your build server used to backtrack the specific commit that a binary is made from. To facilitate this in .NET we have made a ...


4

As you figured out by yourself, SQL is the way to go, but if you put the SQL commands into scripts or embed them in code does actually not make a big difference. What matters is that you make the upgrade process robust. Therefore, I would recommend to consider the following improvement over track your changes in sequential sql or code files Instead, ...


3

Some caveats: You really shouldn't be storing libraries in your source-control system. Especially third-party libraries. Depending on the language and tools that you're using, there are a lot of ways to avoid doing so, but that's another question. Recognize that the Subversion repository uses the equivalent of links internally, so the only time a file is ...


2

I'd keep the data versioned separately. I don't know what your gradual data change workflow is. You could use version control or just named directories, with some sort of de-duplication or plainly. VCSs are usually a poor choice for large binary data. This way you can always check out the data independently of code, and check in code independently of the ...



Only top voted, non community-wiki answers of a minimum length are eligible