On Friday, March 11, 2011 12:41:52 am DaleB wrote: > One last point. > Now, how do i deal best with different versions/branches of my app? Do > you just switch branches while developing or do you use pip in project > env to refer and switch to different tags/branches in your sourcecode. > The first approach feels more dynamic, the latter more 'stable'. In > the end i guess both work, but what do you do? > > Greetings, > Andreas
This is more of a policy situation. What that means is that it can be different. Depends on how you use them. Tags, usually mark a completion point (or milestone). Branches are usually a fork or a radical change or a fork.. In django's history, when they added unicode support through out it, they had the main branch with work being aimed at generally improving django. The unicode branch was were all the changes for adding unicode was done. We as users of django had our choice on what to use, checking out the main tree or the branch with the unicode system. Personally,. I check out branches to a different location than the main project as I consider them different applications. Tags, I just use to mark important milestones for the code I'm working on. Mike -- I'm sorry if the following sounds combative and excessively personal, but that's my general style. -- Ian Jackson -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
