I think we just need to change build_asf script, can you share if there is any 
improvement/tool you would like to see?

The debian/changelog need to be manually fixed since it needs to have a block 
of information including release maintainer name, email, timestamp, package 
name and version which is added on top of this file. I’ve proposed to get rid 
of -snapshot suffixes which cause more problem than benefits.

> On 20-Oct-2014, at 4:16 pm, Erik Weber <terbol...@gmail.com> wrote:
>
> 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 <g...@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.ya...@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.ya...@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 infrastruct...@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
>>

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Infrastructure 
Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Reply via email to