I am curious about whatsource versioning strategy would others apply on a java project (web application) which is very probable to have customization for several customers.
So I am using Subversion as SCM for a classic ASP webapp that I maintain. We use feature branching to handle changes that have dependencies or longer term development.
In a previous job, I found easier to manage and keep a stable pre-release branch (or main, depending on setup) by having each developer work on his/her own branch. We only had a single production inst
I\'m looking for a best practice for the following situation: I have one bll/dal project, and tree UI projects that uses the bll/dal project.
I would like to have some input on how a professional development setup with the following requirements might look like.
The past I develop a software project using subversion as an scm. Until now, development always happened in trunk, so problems arose when a bugfix release was necessary. Now, we want to rethink our b
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this
加载中,请稍侯......