TechNow Ep 26 - Source Control LIVE at Knowledge16

[Chuck Tomasi]

I just got confirmation that we're all set for Wednesday May 18 at 4:00PM on the second floor by the SMCC (social media) area. Come join steppek, dave.slusher and me (ctomasi) to learn about one of our favorite new Helsinki features - Source Control. This is a game changer for developers! More info coming soon on the "Ask the Expert" area.

Update (May 5, 2016): Date corrected. It's May 18, not May 21.

[Viswanatha Red3]

Hi dave.slusher / ctomasi,

Would you please share any guidelines on how to use the source control on a single platform for multiple developers to overcome the list of my concerns [I have stated my concerns in previous comments.]

We are starting to implement SNOW for new client and utilize this functionality and 10 developers will be working parallel.

Thanks & Regards

Viswa

[Chuck Tomasi]

Consider using tagging and branching around sprints/releases, not individual users.

Scenario: You have 250 stories in the sprint. At the end of the sprint, you get 225 done and 6 are in progress. It doesn't matter if this is 1 developer or 20. There is completed work and incomplete work. At some point you say "This is ready for release." Check it in and publish it to the next instance (test, UAT, etc.)

Hope that helps.

[Viswanatha Red3]

Hi ctomasi,

But how to handle the below issue :

          If a developer takes 1 day to fix a bug on different branch, then other developers has to wait till the developer completes his job.

Regards

Viswa

[Chuck Tomasi]

That is correct under the current software architecture. We are discussing various scenarios like the one you mentioned with the platform business unit.