Ending Development
- Changelogic
- Getting Started
- End Development
What does ending development mean?
Ending development is the act of handing over the code to review. By ending development, the developer guarantees that the code conforms to all current quality requirements to his/her best knowledge and implements the tasks that are related with the change.
Ending development is the act of handing over the code to review. By ending development, the developer guarantees that the code conforms to all current quality requirements to his/her best knowledge and implements the tasks that are related with the change.When you have finished editing code for a change and you have verified that your edits work and look as expected, type ant end_edit on command line to signal that the change is ready for review.
There are some situations in which ending development of a change is prohibited:
- there are microchanges planned into the change; please integrate, abandon or replan them
- the state of the change is not “being developed”, for instance, a base version update might be unfinished; finish the other activities
- you are not the owner of the change; please reassign or have the owner end development
When ending development Changelogic does the following:
- any preconditions that have been defined in your project are run
- after that, build script commits your edits and uploads diff to your Changelogic web server
- the status of the change is updated to “awaiting review” and all related tasks are marked as “implementation finished” unless they have other open implementing changes
- the owner of the change is unset
After ending development, the developer may restart development by issuing command ant edit. The developer can do so as long as the review has not begun.