[Asterisk-code-review] mkrelease.py: Certified releases were not being pushed to repo (repotools[master])

[Joshua Colp]

Joshua Colp has uploaded a new patch set (#2).

Change subject: mkrelease.py: Certified releases were not being pushed to repo
......................................................................

mkrelease.py: Certified releases were not being pushed to repo

When making certified releases the script was using the passed in unmodified
project and version as the inputs to the push-release.sh script. This works
fine for a regular Asterisk release. However the passed in certified version
contains a '/'. This made it so when grepping for files they could not be found
since the files were created using a '-' (during the release process the '/'
gets converted at times to a '-'. This patch makes it so the '/' gets replaced
as well when the version is being passed to the push-release.sh script.

Also, the current svn repo where things are stored expects things under
a 'certified-asterisk' directory. The project being passed into the
push-release.sh script was just 'asterisk'. This makes it so the branch
name, in this case 'certified', gets prepended and passed to the script.

Change-Id: I958614904185b3813355c5db7de2ab0182373f07
---
M mkrelease.py
1 file changed, 9 insertions(+), 1 deletion(-)


  git pull ssh://gerrit.asterisk.org:29418/repotools refs/changes/42/2242/2
-- 
To view, visit https://gerrit.asterisk.org/2242
To unsubscribe, visit https://gerrit.asterisk.org/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I958614904185b3813355c5db7de2ab0182373f07
Gerrit-PatchSet: 2
Gerrit-Project: repotools
Gerrit-Branch: master
Gerrit-Owner: Kevin Harwell <kharwell at digium.com>