Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. Source control practices

Source control practices

Scheduled Pinned Locked Moved The Lounge
javascriptpythoncomcollaborationquestion
26 Posts 20 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Dave Kreskowiak

    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 Kreskowiak

    J Offline
    J Offline
    James Curran
    wrote on last edited by
    #21

    Well, 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

    1 Reply Last reply
    0
    • M Marc Clifton

      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

      Sander RosselS Offline
      Sander RosselS Offline
      Sander Rossel
      wrote on last edited by
      #22

      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

      1 Reply Last reply
      0
      • M Marc Clifton

        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

        A Offline
        A Offline
        agolddog
        wrote on last edited by
        #23

        That you continue to be employed there?

        1 Reply Last reply
        0
        • M Marc Clifton

          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

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #24

          "We don't need no stinkin' Devops..."

          "(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal

          1 Reply Last reply
          0
          • C CodeWraith

            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.

            D Offline
            D Offline
            Dominic Burford
            wrote on last edited by
            #25

            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

            1 Reply Last reply
            0
            • M Marc Clifton

              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

              D Offline
              D Offline
              Dominic Burford
              wrote on last edited by
              #26

              Whoever set up those policies needs to taken outside and shot :doh:

              "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

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes

              • Login
              • Don't have an account? Register
              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups