cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Weber <terbol...@gmail.com>
Subject Re: [GitHub] cloudstack pull request: debian: Fix changelog to use 4.4.1 releas...
Date Mon, 20 Oct 2014 10:46:10 GMT
While you are at it Rohit, would it be possible to improve the tools that
set version here and there to include this ( to prevent future issues )?
I guess that would have to go to master and 4.5 as well

-- 
Erik

On Mon, Oct 20, 2014 at 12:26 PM, bhaisaab <git@git.apache.org> wrote:

> GitHub user bhaisaab opened a pull request:
>
>     https://github.com/apache/cloudstack/pull/24
>
>     debian: Fix changelog to use 4.4.1 release with snapshot in the
> version ...
>
>     Both 4.4.0 and 4.4.1 tagged releases have -snapshot in
> debian/changelog resulting in debian package names which should be 4.4.0 or
> 4.4.1 and not 4.4.0-snapshot or 4.4.1-snapshot. This is not the case in
> case of 4.3.1/4.3.0 and past releases. Since 4.4.1 has already been tagged,
> we can keep it this way. Sending this pull request just in case there is
> time to fix it?
>
>     Regards.
>
> You can merge this pull request into a Git repository by running:
>
>     $ git pull https://github.com/apache/cloudstack
> pullrequest-4.4.1-tag-fix
>
> Alternatively you can review and apply these changes as the patch at:
>
>     https://github.com/apache/cloudstack/pull/24.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
>     This closes #24
>
> ----
> commit ebb462b516c708e60edb054f1ca95ff3452e32cb
> Author: Rohit Yadav <rohit.yadav@shapeblue.com>
> Date:   2014-10-20T10:21:44Z
>
>     debian: Fix changelog to use 4.4.1 release with snapshot in the
> version string
>
>     Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
>
> ----
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message