Skip to main content

SVN : Sub Version Repositories.. How to effectively work as a team

Sub Versions are a nice way to manage and Edit a Project as a team. An SVN repository contains the complete code which is to be managed and different people have different rights on accessing and changing the code.
These SubVersions consist of various check points when the code was in a commit state and we can edit these versions or rollback to the previous stable versions and work on them. Hence these repositories help us in managing the code effectively in case a wrong commit is made to the code at any stage.

The commit operations can only be done by authorized people who have access rights on committing a particular file of the project. Read and Write Access can be file as well as project specific.

SVN are pretty common in Unix as well as Windows based machines ( Tortoise SVN ).

EDIT : GIT IS WAY MORE COOLER! FORGET ABOUT THIS! 

Comments

Post a Comment

Popular posts from this blog

Startup founders cheatsheet (Chief product officer)

Define your goals  The basic definition of "mission" and "vision" of the company is critical when we've past the stage of experimenting with the startup's model and helps you prioritise better. From the Expedia page it looks like this: "Our Mission is to Revolutionise Travel Through the Power of Technology", in this case, it is also helping the company know that leveraging and scaling with "technology" is imperative for the company (along with operations). 
Set 2-3 basic targets for the next 2-3 months (possibly 6 months) These might be pretty standard and should align with the mission / vision of the company. If your company wants to be the #1 company in Asia for travel, these basic targets might be: Scale to 100,000 app downloads across platformsIncrease revenue by 15%Increase daily unique visitors to 3 times the current value 
Image Source: Mind the product
Goals help define epics and create a huge backlog Now brainstorming how the targe…