![]() ![]() This information is updated when a UI file is copied from a development server to a live server or visa versa. ![]() FMDIFF 4 FOR MACINTOSH FULLThe version number is displayed on the home page of each solution and, displayed for full access only, large bright text such as ‘LIVE VERSION on xyz server’ or ‘DEVELOPMENT VERSION on zyx server’, etc. Layout text is used to add version numbers, date, person and a summary list describing what has been changed. We use a versioning layout within the UI file. After this, all changes are accompanied with descriptive comments, again dated and by who, along with a ‘changelog’ summary entry in descending date order so the last changes are displayed first. ![]() Other needs include whether a version has been uploaded to the development server for testing only, rather than development, or whether a development version has been removed from the server for offline work (say development during a journey on a laptop).Īll scripts are fully commented and versioned from the date created and by who under a ‘changelog’ comments section located just after the script description comments, which are the first entries. Our requirement for versioning is not for the detail of the work, but to establish which is the live version, which is the development version along with a summary or what work has been carried out for each version. We always use the separation model, hence we have a UI file where the majority of development is carried out, we develop as a team and usually all development work is carried out files hosted on a development server. Version control depends on how the development is carried out and by how many, or at least if by more than one person. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |