May Allah`s peace , mercy and blessing be upon you
"Revision control, also known as version control and source control ... is the management of changes to documents, computer programs, large web sites, and other collections of information". That what wikipedia says about VCS, also in the overview they define a VCS as "... any kind of practice that tracks and provides control over changes to source code."
Today, you can find many great, good, bad and ugly version control systems like Git, Mercurial, Bazzar, SVN, CVS [order is not arbitrary]... but It turns out none of them is good enough for the company, a company that a friend of mine has interned at and told me about their ultimate VCS.
In this company - a well known multinational company that I'm not going to name -, if you want to proceed with a change you don't need to fork or clone or pull. What you do is that you duplicate the lines that you are willing to change, then comment the old ones and put a comment before and after the new code where you put an ID. To get this ID you insert a record in a Microsoft Access database where you specify changes and reasons etc, then you get the ID of that record and put it back in the comment. Changes are copied manually and added to the master if they are correct and god knows what test system they have.
Wow, amazing !! I couldn't believe this reactionary VCS, and what are the reasons behind this choice. And yes I called it a VCS because it's a "... practice that tracks and provides control over changes to source code".
"Revision control, also known as version control and source control ... is the management of changes to documents, computer programs, large web sites, and other collections of information". That what wikipedia says about VCS, also in the overview they define a VCS as "... any kind of practice that tracks and provides control over changes to source code."
Today, you can find many great, good, bad and ugly version control systems like Git, Mercurial, Bazzar, SVN, CVS [order is not arbitrary]... but It turns out none of them is good enough for the company, a company that a friend of mine has interned at and told me about their ultimate VCS.
In this company - a well known multinational company that I'm not going to name -, if you want to proceed with a change you don't need to fork or clone or pull. What you do is that you duplicate the lines that you are willing to change, then comment the old ones and put a comment before and after the new code where you put an ID. To get this ID you insert a record in a Microsoft Access database where you specify changes and reasons etc, then you get the ID of that record and put it back in the comment. Changes are copied manually and added to the master if they are correct and god knows what test system they have.
Wow, amazing !! I couldn't believe this reactionary VCS, and what are the reasons behind this choice. And yes I called it a VCS because it's a "... practice that tracks and provides control over changes to source code".
