Community oriented Programming Advancement.

Uploaded on:
Category: Product / Service
In what manner would we be able to proficiently and precisely join changes to the same record by various ... Microsoft Visual SourceSafe: terrible news. Regular Distributed SCMs. Each WD has a full repo in ...
Slide 1

Paul M. Nguyen CECS-475, Donna Pompei April 28, 2009 Collaborative Software Development

Slide 2

The Problem Many designers chip away at a solitary task? Decide current rendition of code or docs? In what capacity would we be able to productively and precisely consolidate changes to the same record by numerous designers in the meantime? Alternately changes to different records in the meantime? Somebody broke the code; we should retreat to the last form that worked.

Slide 3

The Problem (cont\'d.) What plan contemplations went into this part? Is it accurate to say that someone was wanting to chip away at this segment? What are the huge issues/bugs/highlights that we are concentrating on?

Slide 4

The Solution Collaborative source code administration Collaborative documentation administration Collaborative bug/issue following framework

Slide 5

Source Code Management (SCM) Solves the greater part of the coding issues somehow: Multi-client Builtin Diff instrument Keeps past forms of all records, in a product advancement cognizant way Ability to oversee parallel improvement

Slide 6

Basic Features and Principles Repository (repo): the whole put away history of the task, perhaps with labels Working Directory (WD): more often than not the most recent changes, not as a matter of course in the store Commit: spare WD changes to repo Synchronize: push nearby changes to another archive or force remote changes to the neighborhood vault.

Slide 7

Extended SCM Features Branch: duplicate the vault with the goal that improvement can continue in parallel or veer (branch) and submits can be made in every branch only. Label: Give an exceptional name (typically a rendition number) to a particular correction (the condition of the code) at a point ever

Slide 8

Client-Server SCMs Repository lives on server; customers checkout updates, not the entire archive. CVS: Concurrent Versioning System SVN: Subversion: same theory as CVS, yet nuclear submits and better get to techniques. Microsoft Visual SourceSafe: terrible news

Slide 9

Common Distributed SCMs Every WD has a full repo in it – completely independent storehouse and working index. Git: the SCM utilized for the Linux Kernel Bazaar: made to be anything but difficult to utilize Hg: Mercurial: svn-like interface

Slide 10

Mercurial Very quick; written in Python Can chronicle tip amendment in a straightforward arrangement like Zip or tar.gz and transmitted over FTP or HTTP.

Slide 11

Getting Mercurial You just need the Windows shell augmentation customer: TortoiseHg or the order line customer for Linux or Mac. You can alternatively synchronize your neighborhood work with a focal archive (like BitBucket - agree to a free record)

Slide 12

Mercurial Workflow Pull changes from focal store. Change code; submit changes locally. Pull changes from focal archive. Accommodate any contentions. Push changes to focal archive.

Slide 13

Considerations in CECS Lab You can\'t add the TortoiseHg augmentation to Windows in our labs. You can, in any case, introduce hg to your client account in Linux, and utilize a SSH session while in the Windows labs to control your Mercurial storehouse while working with your records in Windows (they are all in the same spot).

Slide 14

Installation (CECS Account) Download Mercurial doubles for Linux. Place into your ~/tmp index. Unload it with tar xzf {file.tar.gz} Run make introduce home This made a couple of indexes in your home registry and added the executable documents to them.

Slide 15

Post-Install Configuration (CECS) Add two lines to your ~/.cshrc document: set way = ($path ~/canister) setenv PYTHONPATH = ($PYTHONPATH ~/lib/python2.5/site-bundles/hgext ~/lib/python2.5/site-bundles/irregular) Create the record ~/.hgrc with the accompanying substance: [ui] username = Paul M. Nguyen < > Restart your shell with executive csh

Slide 16

BitBucket Mercurial Hosting Provides a focal storehouse for colleagues to clone to their frameworks and redesign against. 150MB Free; numerous donors permitted. SSH-scrambled and verified access to repo.

Slide 17

BitBucket Project Overview

Slide 18

BitBucket Source View

Slide 19

Mercurial Wrap-up Read the Mercurial book at the official site and group at Questions?

Slide 20

Documentation Management For outline contemplations For snappy reference of applicable innovations or comparable tasks For general data utilized by the group as a part of the course of improvement For end-client manuals or guidelines

Slide 21

BitBucket\'s Wiki The Wiki archive worldview is ideal for shared programming advancement – formed, multi-client, online. Easy to utilize

Slide 24

Bug/Issue Tracking Important to have the capacity to track bugs in code and track what endeavors are made to settle these bugs.

Slide 25

BitBucket Issue Tracking BitBucket offers "Issues" highlight to track bugs and status of engineers at settling them.

Slide 26

BitBucket Issue Tracking

Slide 27


View more...