Slide 1
Slide 1 text
(JU
0GG.Z-BXO
Pushing a team to the cutting edge
Slide 2
Slide 2 text
@lee_winder
Slide 3
Slide 3 text
@tenpn
Slide 4
Slide 4 text
PWFSWJFX
reasons for the change
the workflow we adopted
the tools we used
what problems we faced
Slide 5
Slide 5 text
TVSWFZ
we carried out a
to gathers people experience
Slide 6
Slide 6 text
TUBSUFE
where we
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
we stored everything in
Code Assets
Documents SDKs
Slide 11
Slide 11 text
everyone was familiar with
11 out of 13 respondents said they were familiar or very familiar with p4
Slide 12
Slide 12 text
... and everyone else uses
Slide 13
Slide 13 text
6 months to release
long update cycle planned
14+ Developers
Slide 14
Slide 14 text
programmers
artists
designers
QA
UFBNTUSVDUVSF
Slide 15
Slide 15 text
XIZ
change
things?
Slide 16
Slide 16 text
reasons we
decided to
use git
Slide 17
Slide 17 text
JTPMBUFE
feature development
Slide 18
Slide 18 text
XPSLJOH
from home
Slide 19
Slide 19 text
6OJUZ
and Perforce don’t mix
Slide 20
Slide 20 text
DVSJPTJUZ
professional
Slide 21
Slide 21 text
price was never
really a reason
A large number of people thought it was though
Slide 22
Slide 22 text
(JU small and fast
easy branching
writable files
Slide 23
Slide 23 text
XPSLqPX
Feature Branch
QA
Develop
Release
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
http://tinyurl.com/gitflow
Slide 26
Slide 26 text
2"
Feature Branch
Develop
have veto
Slide 27
Slide 27 text
builds all branches
merge manually
builds develop daily
Slide 28
Slide 28 text
JUXBTB
NJTUBLFUP
DPOUJOVPVTMZJOUFHSBUF
BMMCSBODIFT
Slide 29
Slide 29 text
NBOBHFE
branches should have been
rather than a free-for-all
Slide 30
Slide 30 text
UPPMT
are where you’ll sink or swim
Slide 31
Slide 31 text
in general the tools are
QPPS
on Windows
Slide 32
Slide 32 text
GSFF
with client tools
can get you a long way
Slide 33
Slide 33 text
TFSWFS
but it’s worth spending money on your
Gitolite
Slide 34
Slide 34 text
BSUJTUTXPSSJFEBCPVU
UIFMBDLPGBO
FYDMVTJWFDIFDLPVU
but that’s not the fault of the tools really...
A SCS with no exclusive checkout baffles me. I thought that was the point?
Slide 35
Slide 35 text
MBSHF
assets?
but what about
Slide 36
Slide 36 text
PSDs Audio
Excel files Meshs
automated
conversion
Slide 37
Slide 37 text
GVUVSFQSPKFDUTXJMM
VTFTNBMMFSTJCMJOH
HJUSFQPTJUPSJFT
but Perforce will always be required for some assets
Slide 38
Slide 38 text
TNPPUIMZ
it would be boring if it all went
Slide 39
Slide 39 text
initial presentation covered the main differences
Slide 40
Slide 40 text
WPDBCVMBSZ
knocked
everyone
sideways
Slide 41
Slide 41 text
submit
get latest pull
checkout
stage
commit
push
commit
Slide 42
Slide 42 text
DIFDLPVU
Slide 43
Slide 43 text
SFCBTF
we completely ignored
Slide 44
Slide 44 text
NBOZUPPOF
maybe SVN could have been easier to use as the 1 server - N clients logic is easier to
understand than the "each client is also a server" logic
I do not like the two stage process commit/push - I find it redundant and confusing
we clearly didn’t explain the
‘commit to push’ workflow
Slide 45
Slide 45 text
I still don't understand how branches flow in the SourceTree view and that scares me.
Slide 46
Slide 46 text
QFSTPOBMCSBODIFT
a number of developers kept insisting on
Slide 47
Slide 47 text
TDFOFNBOBHFNFOU
XBTPVSCJHHFTUQSPCMFN
exclusive checkout was not the answer
Slide 48
Slide 48 text
DPOTJTUFOUTUPSZ
we should have stuck to a
when speaking to the team
Slide 49
Slide 49 text
IPXUPJNQSPWF
discipline evangelists
uniform tool usage
regular training
consistent story
Slide 50
Slide 50 text
HPPE
CBE
the
and the
Slide 51
Slide 51 text
HPPE
consistently stable builds
strong QA process
flexible working styles
remote working friendly
Slide 52
Slide 52 text
CBE
didn’t provide enough training
initially used poor tools
unstructured branch creation
server support was lacking
Slide 53
Slide 53 text
UPSFDBQ
the experience was generally positive
as the tools improve so will the workflow
we’ll use git on all future projects
we’ll spend more time educating people
Slide 54
Slide 54 text
5IBOLT
Lee Winder
@lee_winder
Andy Fray
@tenpn