Merge ~morphis/snappy-hwe-snaps/+git/build-scripts:f/switch-to-dev-after-release into ~snappy-hwe-team/snappy-hwe-snaps/+git/build-scripts:master

[Simon Fels]

Use new parameter NEXT_VERSION to bump version for the next cycle

[System Enablement Bot (system-enablement-ci-bot)]

PASSED: Continuous integration, rev:94e28047ed2856def922b47b3bcbfb0845415459
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/1281/
Executed test runs:
    SUCCESS: https://jenkins.canonical.com/system-enablement/job/generic-build-snap-worker/362
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/1189/console
    SUCCESS: https://jenkins.canonical.com/system-enablement/job/generic-test-snap/1015

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/1281/rebuild

review: Approve (continuous-integration)

[Konrad Zapałowicz (kzapalowicz)]

ack

review: Approve (code)

[Alfonso Sanchez-Beato (alfonsosanchezbeato)]

Besides the inline comment, I am a bit concerned that we do not know which would be the next version name. We could move from, say PA 8.0 to 9.0 but do not know when doing the release of 8.0-X. If we assume that the version can change in a future commit I guess it is fine though.

review: Needs Fixing

diff --git a/jobs/generic-release-snap b/jobs/generic-release-snap
index 45d7507..62ab7f7 100755
--- a/jobs/generic-release-snap
+++ b/jobs/generic-release-snap
@@ -58,4 +58,10 @@ git push origin stable
 git push origin master
 git push origin $VERSION
 
+git checkout master
+sed -i -e "s/version:\ .*/version: ${NEXT_VERSION}-dev/g" snapcraft.yaml
+git add snapcraft.yaml
+git commit -m "Open development for ${NEXT_VERSION}-dev"
+git push origin master
+
 exec $WORKSPACE/build-scripts/scripts/trigger-lp-build.py -s $SNAP_NAME -p