Source control practices
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Umm. Everything?
Sent from my Amstrad PC 1640 Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Marc Clifton wrote:
What's wrong with this picture?
TFS! You are using TFS!
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
We use TFS for a huge solution and it is fine if it is setup and used properly.
Keep your friends close. Keep Kill your enemies closer. The End
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Let me guess: this is also the official backup system for the company?
Sent from my Amstrad PC 1640 Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Sounds to me like this is the wrong company to be working for. I am sure they are not going to change their ways anytime soon.
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Marc Clifton wrote:
Umm. What's wrong with this picture? ;)
1. - makes the possibility of CI pretty much impossible. 2. - see 1. 3. - see 1. 4. - people need more training. 5. - irrelevance, the number of checkins has no bearing on the validity of trunk -> if your check in breaks trunk you fix it or revert out your changes. Source control done properly is certainly not easy but what you have listed is just as complicated, if not more complicated, as doing source control properly. In addition to 4. - trunk based development is a perfectly valid and at times necessary method of development if you want to be able to deploy at any time when the tests all show green. Branch based development is not necessarily complicated and has its own advantages such as no breaking trunk if you are deploying from trunk.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
GuyThiebaut wrote:
1. - makes the possibility of CI pretty much impossible.
Precisely! If I mention CI around here, I get blank stares or "did you mean the TV show CSI?"
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Let me guess: this is also the official backup system for the company?
Sent from my Amstrad PC 1640 Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
OriginalGriff wrote:
this is also the official backup system for the company?
Actually no - that seems to be handled fairly well.
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
GuyThiebaut wrote:
1. - makes the possibility of CI pretty much impossible.
Precisely! If I mention CI around here, I get blank stares or "did you mean the TV show CSI?"
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
There are people with intellects far superior to mine who struggle with implementing CI. It's a long process to get there and I can only claim to understand some of the principles. However, even if CI is not the end goal, having everything in one solution is really not a very good idea nowadays given all the tools(Nuget etc) and experience documented on how to reduce risk and do things 'properly'. Your post also makes me grateful that I work somewhere that has fairly decent source control practises - that said it took me a good 6 months to really absorb how to do source control properly - using project branches, a trunk, release candidate branches etc.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
There's a [word](https://en.wiktionary.org/wiki/clusterfuck) for that
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
a single SLN
Marc Clifton wrote:
Umm. What's wrong with this picture?
Always use married SLNs they are more stable and reliable. ;P
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
-
Marc Clifton wrote:
a single SLN
Marc Clifton wrote:
Umm. What's wrong with this picture?
Always use married SLNs they are more stable and reliable. ;P
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
No, they're easier to blackmail.
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
Umm. What's wrong with this picture? ;)
That sounds more like a Jackson Pollock painting than a picture... :)
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Bloody hell, I thought our source control was lousy, I'm going to have to apologise to the dev who manages it :-O
Never underestimate the power of human stupidity RAH
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
That doesn't sound like they have much 'control' over their source code :sigh: A chainsaw is worse than a regular saw if you insist on manually moving it back-and-forth over the wood instead of powering it up :wtf:
Up, Up, Down, Down, Left, Right, Left, Right, B, A.
-
All that crap and manual work and they say its the whole BRANCH thing is too complicated. :wtf:
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakWell, branching on TFS does suck. That's probably GIT's primary advantage over TFS. (GIT's distributed nature is useful is a massive diverse project like Linux, but of really little use in most places)
Truth, James
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Wow. Much professional. Such knowledge. Very good programmers.[^] Why do these people even have a job in programming? :sigh:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
State of affairs (this is with TFS, Git is not used): 1. All projects, regardless of how unrelated, are in a single SLN 2. When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects. 3. After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod. 4. The branching policy stands as: "branches are too complicated" 5. The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work." Umm. What's wrong with this picture? ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Marc Clifton wrote:
What's wrong with this picture?
TFS! You are using TFS!
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
TFS is not the problem. The same policies would still exist if using Github or another tool. The problem is how TFS is being used.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
