General discussion
Thread display: Collapse - |
All Comments
Start or search
Create a new discussion
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Development Environment Code Management
However, we also have a Base version (from which new releases previously mentioned are cloned) from which we create software revisions and releases. Theoretically, customizations made in client environments are integrated intothe Base system once the implementation project is complete.
Time and money constraints often mean that code integration to Base is not performed in a timely fashion. Two problems emerge because of this situation:
1. Work (for example bug fixes) already performed in Base need to be duplicated in client environments (because a client changes have not been integrated into base so a patch can not be issued); and
2. Work preformed in a client system needs to be performed in another clientsystem because (because a client changes have not been integrated into base a copy of base has to be augmented with the changes).
We are considering moving to a system in which there is only one environment in which development work takes place (Base). However I am concerned that we will experience issues with contention for code objects, etc.
Does anyone have feedback or advice on how we can rationalize the effort that we invest in internal code merging and management? How can we best balance effort spent moving code between environments with considerations like conflict for source code objects?