Revision Control Systems Recommendation, Setup & Training

キャンセルされた 投稿 Oct 25, 2012 着払い
キャンセルされた 着払い

Need to implement a revision control system. I need someone with experience with many revision Control systems.

I am the Business Analyst, Business Systems Analyst and PM and I have not used a SVC or VCS or Subversion of GIT. I guess it needs to be the BEST tool that will really help different teams of developers that may use some of the same programs. This is not for a large project. Total number of developers under ten.

Main concern is merging code and controlling the code for different releases, tagging. I'd like a GUI management layer that is more graphical where I can monitor progress and what is going on

It may also be necessary to develop two versions of the software concurrently (for instance, where one version has bugs fixed, but no new features (branch), while the other version is where new features are worked on (trunk)

I think if it can tie in with a bug tracking tool that would be great as well. We are currently using OnTimeNow for tracking bugs.

Our development environment is LAMP. Now I don't fully understand how all this works but developers may or may not have a server. Can this work so that developers can work on their home PCs running windows or develop on the home server and to control and merge the programs for the application website server?

Also you will need to train me. I am a fast learner and have been in IT for over 15 years+ so I should pick it up but I need to learn better to Master this QUICKLY

Your ability to communicate, explain, teach with an excellent level of English is mandatory. This needs to start ASAP. I can't wait a week to start maybe a few days max

It does not have to be a FREE product just the BEST tool out there that may have a level for management that is easy to use

Centralized model works for backup, undo and synchronization but isn't great for merging and branching changes people make. As projects grow, you want to split features into chunks, developing and testing in isolation and slowly merging changes into the main line. In reality, branching is cumbersome, so new features may come as a giant checkin, making changes difficult to manage and untangle if they go awry

Sure, merging is always "possible" in a centralized system, but it's not easy: you often need to track the merge yourself to avoid making the same change twice. Distributed systems make branching and merging painless because they rely on it.

With the proper layout a DVCS can do anything a centralized system can, with the added benefit of easy merging.

Advantages

Everyone has a local sandbox. You can make changes and roll back, all on your local machine. No more giant checkins; your incremental history is in your repo.

It works offline. You only need to be online to share changes. Otherwise, you can happily stay on your local machine, checking in and undoing, no matter if the "server" is down.

It's fast. Diffs, commits and reverts are all done locally. There's no shaky network or server to ask for old revisions from a year ago.

It handles changes well. Distributed version control systems were built around sharing changes. Every change has a guid which makes it easy to track.

Branching and merging is easy. Because every developer "has their own branch", every shared change is like reverse integration. But the guids make it easy to automatically combine changes and avoid duplicates.

Less [url removed, login to view]'s no "always-running" server software to install.

Disadvantages

With a DVCS, you still want a machine to push changes to "just in case". (In Subversion, you usually dedicate a machine to store the main repo; do the same for a DVCS).

Again, a central location helps clarify what the latest "stable" release is.

Thankfully, you can tag releases with meaningful names.

I live in Mountain Time Zone so you will need to be available during my hours. I hope that 2 hours a day for week will do it.

We will use whatever tool is selected.

アジャイル開発 プロダクトマネジメント プロジェクト管理 ソフトウェアアーキテクチャ ウェブサイト管理

プロジェクトID: #2596374

プロジェクトについて

3個の提案 リモートプロジェクト アクティブ Nov 5, 2012