Comments on: 5 SVN best practices http://www.iovene.com/21/ The thoughts of a computer programmer, open source supporter, astrophotographer and free-thinker. Tue, 15 May 2012 22:40:29 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Blog ScrumHalf - Algumas Boas Práticas no Controle de Versão http://www.iovene.com/21/#comment-198569 Blog ScrumHalf - Algumas Boas Práticas no Controle de Versão Thu, 29 Mar 2012 01:34:31 +0000 http://www.iovene.com/wordpress/?p=21#comment-198569 [...] 5 SVN best practices [...] [...] 5 SVN best practices [...]

]]> By: Algumas Boas Práticas no Controle de Versão | Blog ScrumHalf - Gerência de Projetos Ágeis e Scrum - Brasil http://www.iovene.com/21/#comment-174769 Algumas Boas Práticas no Controle de Versão | Blog ScrumHalf - Gerência de Projetos Ágeis e Scrum - Brasil Thu, 01 Dec 2011 17:49:21 +0000 http://www.iovene.com/wordpress/?p=21#comment-174769 [...] 5 SVN best practices [...] [...] 5 SVN best practices [...]

]]> By: Saqib Khan http://www.iovene.com/21/#comment-130757 Saqib Khan Sun, 15 May 2011 13:34:08 +0000 http://www.iovene.com/wordpress/?p=21#comment-130757 Hi, We have recently shifted from VSS to SVN along with the migration. In case of any help is required, feel free to contact at saqib6111@hotmail.com. Thanks! Saqib Hi,
We have recently shifted from VSS to SVN along with the migration. In case of any help is required, feel free to contact at saqib6111@hotmail.com.

Thanks!

Saqib

]]> By: Salvatore Iovene http://www.iovene.com/21/#comment-118476 Salvatore Iovene Tue, 15 Feb 2011 19:16:39 +0000 http://www.iovene.com/wordpress/?p=21#comment-118476 Hi. The easiest way to deal with these kind of things is to branch each time you tag a major revision. You could have trunk, then branch 1.0, then tag 1.0. You could make the fix in trunk if it's not already fixed, then port it to the 1.0 branch, and tag 1.0.1, or 1.0.2, or whatever it is. With git you would cherry-pick. Hi. The easiest way to deal with these kind of things is to branch each time you tag a major revision.

You could have trunk, then branch 1.0, then tag 1.0.

You could make the fix in trunk if it’s not already fixed, then port it to the 1.0 branch, and tag 1.0.1, or 1.0.2, or whatever it is.

With git you would cherry-pick.

]]> By: Eddie http://www.iovene.com/21/#comment-118435 Eddie Tue, 15 Feb 2011 14:05:13 +0000 http://www.iovene.com/wordpress/?p=21#comment-118435 Nice article. Can you relate to the following scenario ? 1) Version 1.0 released. 2) Development is continued on trunk. 3) A customer report a bug in 1.0. How would you recommend going about it in terms of branches/tags/Merges. Thanks much ! Nice article. Can you relate to the following scenario ?
1) Version 1.0 released.
2) Development is continued on trunk.
3) A customer report a bug in 1.0.

How would you recommend going about it in terms of branches/tags/Merges.

Thanks much !

]]> By: Boas Práticas na Utilização de Controle de Versão « Luizgustavoss's Weblog http://www.iovene.com/21/#comment-108376 Boas Práticas na Utilização de Controle de Versão « Luizgustavoss's Weblog Thu, 09 Sep 2010 17:36:04 +0000 http://www.iovene.com/wordpress/?p=21#comment-108376 [...] http://www.iovene.com/21 Deixe um comentário [...] [...] http://www.iovene.com/21 Deixe um comentário [...]

]]> By: NAPLAN http://www.iovene.com/21/#comment-105498 NAPLAN Tue, 18 May 2010 01:58:10 +0000 http://www.iovene.com/wordpress/?p=21#comment-105498 I use Visual Source Safe; but would like to move onto SVN but finding it hard to setup! anyhow nice article thanks; I use Visual Source Safe; but would like to move onto SVN but finding it hard to setup! anyhow nice article thanks;

]]> By: Salvatore Iovene’s 5 SVN Best Practices | Nstein Support Network http://www.iovene.com/21/#comment-103189 Salvatore Iovene’s 5 SVN Best Practices | Nstein Support Network Thu, 28 Jan 2010 15:31:34 +0000 http://www.iovene.com/wordpress/?p=21#comment-103189 [...] Salvatore 5 best practices: [...] [...] Salvatore 5 best practices: [...]

]]> By: SubVersion Best Practices « Bradford Systems Blog http://www.iovene.com/21/#comment-102996 SubVersion Best Practices « Bradford Systems Blog Thu, 14 Jan 2010 23:22:04 +0000 http://www.iovene.com/wordpress/?p=21#comment-102996 [...] Never ever break the trunk. Source [...] [...] Never ever break the trunk. Source [...]

]]> By: ::: » Flex and SVN mxml.it ::: avoid mickey mouse programming ::: http://www.iovene.com/21/#comment-41224 ::: » Flex and SVN mxml.it ::: avoid mickey mouse programming ::: Tue, 14 Oct 2008 16:07:10 +0000 http://www.iovene.com/wordpress/?p=21#comment-41224 [...] http://blog.evanweaver.com/articles/2007/08/15/svn-branching-best-practices-in-practice/ http://www.iovene.com/5-svn-best-practices/ http://svnbook.red-bean.com/en/1.4/svn.tour.cycle.html http://www.changelogic.com/SvnProjectSetup [...] [...] http://blog.evanweaver.com/articles/2007/08/15/svn-branching-best-practices-in-practice/ http://www.iovene.com/5-svn-best-practices/ http://svnbook.red-bean.com/en/1.4/svn.tour.cycle.html http://www.changelogic.com/SvnProjectSetup [...]

]]>