 -Develop_Begin(1)

NAME
-Develop_Begin - begin development of a change

SYNOPSIS
-Develop_Begin change-number [ option... ]
-Develop_Begin -List [ option... ]
-Develop_Begin -Help

DESCRIPTION
The -Develop_Begin command is used to commence development of a change.

The development directory for the change will be created automatically; below the directory specified in the default_development_directory field of aeuconf(5), or if not set below the directory specified in the default_development_directory field of aepattr(5), or if not set below the current user's home directory. It is rare to need to know the exact pathname of the development directory, as the aecd(1) command can take you there at any time.

Successful execution of this command will move the specified change from the awaiting development state to the being developed state.

  Notification
The develop_begin_command in the project config file (see aepconf(5) for more information) will be run, if specified. This is run after the aegis locks are released, so additional aegis commands may be run from here, if used with care. The symbolic links (see below) have not yet been created.

  Development Directory Location

ADMINISTRATOR OVERRIDE
It is possible for project administrators to use the -User option to force a developer to start developing a change. Some sites prefer to work this way. Note that developers still have the ability to use the aedbu(1) command.

Warning: capricious use of this command will rapidly alienate developers. The defaulting rules, particularly for the change number, depend on and the developer agreeing on what the developer is currently working on.

The forced_develop_begin_notify_command project attribute (see aepattr(5) for more information) will be run when an administrator uses the -User option, in an attempt to minimize the surprises for developers. A suitable command is
    forced_develop_begin_notify_command =
        "$datadir/db_forced.sh $p $c $developer";
This command will send e-mail to the developer, informing her that the change has been assigned to her.

OPTIONS
The following options are understood: This option may only be used by a project administrator.

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

ERRORS
It is an error if the change does not exist.
It is an error if the change is not in the awaiting development state.
It is an error if the current user is not a developer of the specified project.

SEE ALSO

aeb(1)
    build a change

aecd(1)
    change directory

aecp(1)
    copy files into a change

aed(1)
    find differences between a change and the baseline

aedbu(1)
    undo the effects of aedb

aede(1)
    complete development of a change

aemv(1)
    rename a file as part of a change

aenc(1)
    add a new change to a project

aend(1)
    add a new developer to a project

aenf(1)
    add new files to a change

aent(1)
    add a new test to a change

aepa(1)
    modify the attributes of a project

aerm(1)
    add files to be deleted to a change

aet(1)
    run tests

aepattr(5)
    project attributes file format

aeuconf(5)
    user configuration file format