After getting used to some very basic git commands, dealing with changes to access is rather cumbersome because you just have to copy changes over from test to live. Or at least, that's how I've been doing it.
...
Are there any solutions besides manual documentation?
Hi ZenMasta,
With my (I counted them) 88 applications, it is very hard to document what the status of each application is, and what the changes are/were. So I developped a technique that all this can be done dynamically, where the software itself is the source of the
documentation.
When the user gets a new version, he gets a (compiled) copy of the application that I use for development. In fact this user gets Always the "latest" version.
To do my developping work I set a global boolean indicating that the application is in the development mode. I can build in new code using a construction like:
If (glo_dev) Then
new code lines
Else
Original code lines
End If
In this way I can develop and check new parts, while, when installing this before the new code is completely finished, the user won't "see" it. After accepting the new code the line "If (glo_dev") Then" is converted to "If
(TRUE) Then". And after some time I do the clean up to remove the Original (old) code.
The situation is even more complex in my case, while every application shares a referenced library database with generalized functionaity that accounts for more then 95% of all the code that is used. The library database changes continuously to add
more functionality, or improve it.
With this way of working I have no problems with version control. A user gets always the "hottest" version of his application, But it depends of the glo_dev value what is available to the user.
Imb.
