diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2019-09-19 16:03:42 +0200 |
|---|---|---|
| committer | laforge <laforge@gnumonks.org> | 2019-09-20 15:11:03 +0000 |
| commit | a6097132462ed053f1a699174d4625c7d4ae25eb (patch) | |
| tree | 3d67464a1753a9c967490ca7a6d97dd45a8e58f8 | |
| parent | ae140bc84a3cc771d730a0ab8522707773eb8c0d (diff) | |
osmo-release.sh: update TODO-RELEASE for non-lib projects too
Projects not containing libraries may also want to contain a
TODO-RELEASE in order to write down when a new API available only on
libosmoXYZ current master (hence configure.ac and debian cannot be
updated during the patch using the API until the APIs are available in a
new release). This way, during release process of the project, the
maintainer can see that a release of libosmoXYZ is needed beforehand and
then update configure.ac of project accordingly with the new version of
libosmoXYZ.
Furthermore, we want to update the file only if mode DRY_RUN is not
selected.
Change-Id: I409b7eb8c23d21473f25dd2000f5d4447b24adb9
| -rwxr-xr-x | osmo-release.sh | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/osmo-release.sh b/osmo-release.sh index 1effe7e2..44504360 100755 --- a/osmo-release.sh +++ b/osmo-release.sh @@ -156,16 +156,18 @@ if [ "z$LIBVERS" != "z" ]; then if [ "z$DRY_RUN" != "z0" ]; then exit 0 fi - if [ -f "TODO-RELEASE" ]; then - grep '#' TODO-RELEASE > TODO-RELEASE.clean - mv TODO-RELEASE.clean TODO-RELEASE - git add TODO-RELEASE - fi fi if [ "z$DRY_RUN" != "z0" ]; then exit 0 fi + +if [ -f "TODO-RELEASE" ]; then + grep '#' TODO-RELEASE > TODO-RELEASE.clean + mv TODO-RELEASE.clean TODO-RELEASE + git add TODO-RELEASE +fi + gbp dch --debian-tag='%(version)s' --auto --meta --git-author --multimaint-merge --ignore-branch --new-version="$NEW_VER" dch -r -m --distribution "unstable" "" git add ${GIT_TOPDIR}/debian/changelog |