Good practice to make the .exe and .dll have the same version?
For a new release I increase the version number of the executable, should I make all the dll have the same version number as the executable even if the dll is not updated at all? ...
For a new release I increase the version number of the executable, should I make all the dll have the same version number as the executable even if the dll is not updated at all? ...
Let's say you work on a large project with multiple features targeted in each release. We may have different feature branches (in the VCS) for each feature development. But after all the feature branch is merged and integration is done say one of the feature is dropped (this happens more frequently in our organization than you would imag...
Hi, I have no problem creating software. I have dozens of projects that I would be more than happy to release to the public. The problem is that after I put the finishing touches on something (eg final release build), I end up blocked because it’s not as simple as just putting an EXE on the Internet for people to download. I have diffic...
What we need in our firm is a sort of release management tool for Linux/C++. Our products consist of multiple libraries and config files. Here I will list the basic features we want such system to have: Ability to track dependencies, easily increase major versions of libraries whose dependencies got their major version increased. It sh...
Hudson CI server displays stability "weather" which is cool. And it allows one project build to kick off based on the successful build of another. However, how can you make that secondary project dependent additionally on the stability of multiple builds of the first project? Specifically, project "stable_deploy" needs to only kick off ...
Having read Martin Fowlers "Feature Branch" and Flickrs "Flipping Out" I guess there are a few guys out there who do: all (or most) development on Trunk release Trunk regularly (assuming updating your web site) not-yet-approved or not-yet-finished features should not be visible/have no impact on the regular user I've got 2 questions:...
I'm working on a product which relies on several different projects each hosted in its own Git repository. When a release is made, it would be ideal for us to consistently tag every project that is involved in building the product - this includes the core code, libraries and build tools. Is there an obvious and sensible way to tag all ...
To release my centralized webapp, I COULD have a vhost pointed to some directory and then just do a 'git pull' when I want to release, updating the files. But Rails has a different deployment mechanism: it copies files to a subdirectory and then points a symlink ('current') to that new subdirectory. I understand that it probably more ac...
Our group is currently analysing our procedures for managing formal software releases and integrating with a bug lifecycle. What bug lifecycle model do you use? And why? For example assume a that formal releases are generated for QA once per week. At what point do you mark bugs as resolved? When the developer has committed their chan...
Hello, I look after the merging, deployment and release of Products & Services in the Company I work for. I've slowly moved to this position from development so a lot of this is new to me (I guess!) We have a deployment process, but no real Release procedure other than telling stakeholders and members of staff about these new services/...
The process of creating a new build and releasing it to production is a critical step in the SDLC but it is often left as an afterthought and varies greatly from one company to the next. I'm hoping people will share improvements they have made to this process in their organisation so we can all takes steps to 'reduce the pain'. So the...
When using the maven-release-plugin with Git, mvn release:prepare happily tags the release in the local repository. I'd expect mvn release:perform to push the tags to the remote repository, but this doesn't seem to happen. Am I mistaken? If not, is there an option to enable pushing release tags to the remote repository? ...
I have a repository that is running subversion. Some users have not been committing regularly. I'd like to send out a weekly reminder to those that have not committed during the last week. Is there a way to determine when each users last submit date was? ...
Hi Guys, I was wondering how to "Exclude" individual files in the "release" web.csproj config of my solution. I've seen other answers and they all feature "include" - but this is not what I am wanting to achieve. I only want to exclude around 10-15 files from a "release" package ? I don't want to manually edit the web.csproj file - so ...
Tipically a deploy in production does not involve just a mere source code update (build) but requires a lot of other important tasks like, for example: Db scripts Configuration files (differents from test\production) Batch to schedule Executables to move to the correct path Etc. etc. In our company we just send an email to a "Release...
Do you know of any agile process that is created for code releases? One of the main theme of agile is frequent releases and each company/client would have their own test/approval processes that control code releases. Most of the time these slow down the pace of "frequent releases" Currently we have a proprietary tool based workflow. The...
I want to throw this scenario out there and see what the most objective, vanilla-Mercurial way to fix this would be. Suppose I have the following branches in my centralized Mercurial repository for my centralized, non-distributed web-app: repository default feature1 feature2 bugs Suppose ten developers have committed ...
Our system comprises many .NET websites, class libraries, and a MSSQL database. We use SVN for source control and TeamCity to automatically build to a Test server. Our team is normally working on 4 or 5 projects at a time. We try to lump many changes into a largish rollout every 2-4 weeks. My problem is with keeping track of all the ...
My shop is trying to formalize the release management process for an OSS product we maintain (edit: using SVN for version control). It's a sort of a web development framework/CMS kind of thing, as in it's a product that other projects are built on top of. This makes clear communication about the versioning system especially critical for ...
I am creating a process for working with version control and my web based application. This is what I have so far: I am doing main development under branches/development and keep that in sync with my development server for testing. I use svn:externals to bring the Zend Framework into my project. I use the revision number from the tag...