 -Develop_End(1)

NAME
-Develop_End - complete development of a change

SYNOPSIS
-Develop_End [ option... ]
-Develop_End -List [ option... ]
-Develop_End -Help

DESCRIPTION
The -Develop_End command is used to notify of the completion of the development of a change.

This command checks that you have successfully completed an ' -Build' command since any change source file was edited. See aeb(1) for more information.

This command checks that you have successfully completed an ' -DIFFerence' command since any change source file was edited. See aed(1) for more information.

This command checks that you have successfully completed an ' -Test' command since the last successful build, unless the change has a test_exempt attribute, or the build command is "exit 0". This command checks that you have successfully completed an ' -Test -BaseLine' command, unless the change has a test_baseline_exempt attribute. This command checks that you have successfully completed an ' -Test -REGression' command, unless the change has a test_regression_exempt attribute. See aet(1) and aecattr(5) for more information.

If the change includes the project configuration file, this command checks project file names, to make sure they conform to the maximum_filename_length and posix_filename_charset field settings. See aepconf(5) for more information.

Successful execution of the command advances the change from the being developed state to the being reviewed state, by default. The develop_end_action project attribute controls which of the following 3 paths are taken. Please Note: the third alternative, skipping reviews altogether, should only be used for single person projects. All self-respecting commercial enterprise will avoid this alternative.

Because branches may extend for many months or even years, it is common for the user who initiated the branch to be no longer with the project, or even the company. For this reason, project administrators may end the development of branches. For normal changes in this situation, use the aechown(1) command.

If the project configuration file has specified the presence of Signed-off-by: lines, a suitable line containing the current user's email address will be appended to the change description.

The change is no longer considered assigned to the developer.

  Branches
If you get an error message telling you that you can't end a branch because a file needs to be merged, see the Branching chapter of the Aegis User Guide for more information.

While changes and branches are almost identical in the ways you manipulate them within Aegis, actual file changes must always be done in a change. Thus, it is necessary to create a new change on the branch and do a cross-branch grandparent merge before you will be able to develop-end a branch which is giving you this error.

  Notification
On successful completion of the command, the develop_end_notify_command field of the project attributes file is run, if set. See aepa(1) and aepattr(5) for more information.

If your project has configured the develop_end_action in the project confifuration file to goto_awaiting_integration then the review_pass_notify_command in the project attributes file is run instead, if set.

OPTIONS
The following options are understood:

RECOMMENDED ALIAS
The recommended alias for this command is
csh%	alias aede ' -de \!* -v'
sh$	aede(){ -de "$@" -v}

ERRORS
It is an error if the change is not assigned to the current user.
It is an error if The change is not in the being developed state.
It is an error if there has been no successful ' -Build' command since a change file was last edited.
It is an error if there has been no successful ' -DIFFerence' command since a change file was last edited.
It is an error if there has been no successful ' -Test' command since a change file was last edited.
It is an error if there has been no successful ' -Test -BaseLine' command since a change file was last edited.

It is an error if an read-only file is still copied into the change. Read-only files are to insulate a change from the baseline during development; they must be removed before development may end.

SEE ALSO

aeb(1)
    build a change

aeca(1)
    list or modify attributes of a change

aed(1)
    difference a change

aedb(1)
    begin development of a change

aede-policy(1)
    validate change set is ready to end

aedeu(1)
    recall a change for further development

aerfail(1)
    fail a change review

aerpass(1)
    pass a change review

aet(1)
    test a change

aepconf(5)
    project configuration file format

aeuconf(5)
    user configuration file format