You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Chip Childers <ch...@sungard.com> on 2012/10/05 17:50:39 UTC
What specifically needs to change in debian/changelog for a 4.0.0 release?
Wido,
When we cut a 4.0.0 release build to vote on next, what exactly needs
to change in the debian/changelog file to mark it as 4.0.0 "stable".
I'm not familiar enough with deb packaging to know what I'm looking
at. We need to document that in a release process, as well as ensure
that the artifact that we vote on has the right bits in the right
places.
Thanks!
-chip
Re: What specifically needs to change in debian/changelog for a 4.0.0
release?
Posted by Wido den Hollander <wi...@widodh.nl>.
On 10/05/2012 09:52 PM, Chip Childers wrote:
> Wido,
>
> I think I figured it out. Please double check debian/changelog in
> master and 4.0 branches for me though.
>
No, not completely.
The version has to be something like: 1:4.0.0-1
Otherwise apt and dpkg will thing that the beta6 version is even newer.
I'll push a commit for this.
Wido
> -chip
>
>
> On Fri, Oct 5, 2012 at 11:50 AM, Chip Childers
> <ch...@sungard.com> wrote:
>> Wido,
>>
>> When we cut a 4.0.0 release build to vote on next, what exactly needs
>> to change in the debian/changelog file to mark it as 4.0.0 "stable".
>>
>> I'm not familiar enough with deb packaging to know what I'm looking
>> at. We need to document that in a release process, as well as ensure
>> that the artifact that we vote on has the right bits in the right
>> places.
>>
>> Thanks!
>>
>> -chip
Re: What specifically needs to change in debian/changelog for a 4.0.0 release?
Posted by Chip Childers <ch...@sungard.com>.
Wido,
I think I figured it out. Please double check debian/changelog in
master and 4.0 branches for me though.
-chip
On Fri, Oct 5, 2012 at 11:50 AM, Chip Childers
<ch...@sungard.com> wrote:
> Wido,
>
> When we cut a 4.0.0 release build to vote on next, what exactly needs
> to change in the debian/changelog file to mark it as 4.0.0 "stable".
>
> I'm not familiar enough with deb packaging to know what I'm looking
> at. We need to document that in a release process, as well as ensure
> that the artifact that we vote on has the right bits in the right
> places.
>
> Thanks!
>
> -chip