NAME

make-release - automatic make of a new release of a package, setting the next branch release version, adding a comment, tagging the branch, pushing it to the remote repository, queueing and running the build task for it.

SYNOPSIS

make-release [Options] [<branch name>]

DESCRIPTION

make-release makes a new release branch and tag modifying the package release version accordingly to the build policy. Control of the remote build task can be done with the use of the corresponding options.

make-release uses the git configuration file. The following variables are read:

* girar.remote, corresponding to --remote;

OPTIONS

-R,--remote=NAME

girar server alias, defaults to git.alt;

-o,--origin=NAME

use NAME instead of 'origin' to set up git remote;

-M,--merge[=NAME]

merge branch with the master branch (default: `master');

-b,--build

create and run a remote build task, implies -t;

-t,--task[=NUM[:SUBNUM]] create a remote build task or add entry to a task NUM,

optionally the subtask id can be specified;

-C,--committer=DATA information about the committer (i.e. full name <email>);

-m,--message=MSG

changelog message;

-d,--dry-run

output information, do not make any changes (implies -v);

-p,--push

push modifications to the remote repository;

-f,--force

ignore warnings and continue;

-T,--test

create and run a remote test build task, implies -b;

-c BUGS,

--closes=BUGS

add "closes" clause to the changelog with BUGS as bug number list;

-q,--quiet

try to be more quiet;

-v,--verbose

print a message for each action;

-V,--version

print program version and exit;

-h,--help

show this text and exit.

ENVIRONMENT

GIT_DIR

If the GIT_DIR environment variable is set then it specifies a path to use instead of the default for the base of the repository.

AUTHOR

Written by Paul Wolneykien <manowar@altlinux.org>

REPORTING BUGS

Report bugs to http://bugs.altlinux.ru/

COPYRIGHT

Copyright © 2009 Paul Wolneykien <manowar@altlinux.org>
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

SEE ALSO

git-config(1), gear(1), git-push(1).