mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] make_release.sh: make it more accessible for creating custom releases
Date: Wed, 12 Feb 2014 09:54:44 +0100	[thread overview]
Message-ID: <20140212085444.GF4551@pengutronix.de> (raw)
In-Reply-To: <1391630133-20347-2-git-send-email-jon@ringle.org>

On Wed, Feb 05, 2014 at 02:55:33PM -0500, jon@ringle.org wrote:
> From: Jon Ringle <jringle@gridpoint.com>
> 
> Without args, the script will continue to work as it used to for
> pengutronix approved releases
> 
> But now a custom release can be created if your in a situation where you
> need to distribute to a group of developers a needed fix to ptxdist and
> you can't wait until the next pengutronix release of ptxdist.
> 
> I've personally setup my local ptxdist.git repo to use gitflow-AVH:
> 
> [gitflow "branch"]
>         master = production
>         develop = develop
> [gitflow "prefix"]
>         feature = feature/
>         release = release/
>         hotfix = hotfix/
>         support = support/
>         versiontag = gp-
> 
> I will then call this script from the production branch like this:
> $ git checkout production
> $ ./scripts/make_release.sh gridpoint production release GP -a
> 
> and if I need a subsequent release within the same month:
> $ git flow release start ptxdist-2014.02.x_GP
> $ ./scripts/make_release.sh gridpoint production release GP -a
> 
> Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> ---
>  scripts/make_release.sh |   29 ++++++++++++++++++-----------
>  1 file changed, 18 insertions(+), 11 deletions(-)
> 
> diff --git a/scripts/make_release.sh b/scripts/make_release.sh
> index f0d4357..3c8a555 100755
> --- a/scripts/make_release.sh
> +++ b/scripts/make_release.sh
> @@ -2,7 +2,14 @@
>  
>  set -e
>  
> -origin=origin
> +origin=${1:-origin}
> +master=${2:-master}
> +stable=${3:-stable}
> +suffix=${4:-}
> +tagsignopt=${5:--s}

This makes things really confusing. Use 'getopt' including '-h' I think.

Michael

> +
> +[ -n "${suffix}" ] && suffix="_${suffix}"
> +
>  v="ptxdist-"
>  
>  branch="$(git symbolic-ref HEAD)"
> @@ -29,23 +36,23 @@ fi
>  
>  # guess if we're going to make a new or stable release
>  case "${branch}" in
> -    master)
> -	release="${v}$(date +%Y.%m).0"
> -	prev_release="${v}*.0"
> +    ${master})
> +	release="${v}$(date +%Y.%m).0${suffix}"
> +	prev_release="${v}*.0${suffix}"
>  	;;
> -    stable/*)
> -	release="${branch##stable/}"
> -	release="${release%.x}"
> +    ${stable}/*)
> +	release="${branch##${stable}/}"
> +	release="${release%.x${suffix}}"
>  	inc="$(git tag -l "${release}.*" | wc -l)"
>  	if [ ${inc} -eq 0 ]; then
>  	    echo "about to make stable a release for '${release}', but no '.0' found" >&2
>  	    exit 1
>  	fi
> -	prev_release="${release}.$((inc - 1))"
> -	release="${release}.${inc}"
> +	prev_release="${release}.$((inc - 1))${suffix}"
> +	release="${release}.${inc}${suffix}"
>  	;;
>      *)
> -	echo "please checkout either master or stable branch" >&2
> +	echo "please checkout either ${master} or ${stable} branch" >&2
>  	exit 1
>  	;;
>  esac
> @@ -70,7 +77,7 @@ log="${tmp}/log"
>  printf "${release}\n\n" > "${log}"
>  git shortlog "${prev_release}"..HEAD >> "${log}"
>  echo "creating tag '${release}'"
> -git tag -s -F "${log}" "${release}"
> +git tag ${tagsignopt} -F "${log}" "${release}"
>  
>  # create tarball
>  here="$(pwd)"
> -- 
> 1.7.10.4
> 
> 
> -- 
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-02-12  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 19:55 [ptxdist] [PATCH] ptxd_make_get.sh: remove git fetch --progress jon
2014-02-05 19:55 ` [ptxdist] [PATCH] make_release.sh: make it more accessible for creating custom releases jon
2014-02-12  8:54   ` Michael Olbrich [this message]
2014-02-06  1:21 ` [ptxdist] [PATCH] ptxd_make_get.sh: remove git fetch --progress Jon Ringle
2014-02-12  8:51   ` Michael Olbrich
2014-02-13 14:08 [ptxdist] [PATCH] make_release.sh: make it more accessible for creating custom releases jon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140212085444.GF4551@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox