[patch] Bump release [Was: apt-rpm 0.5.15lorg3.2 released!]

[Panu Matilainen]

On Thu, 22 Jun 2006, Ralf Corsepius wrote:

> On Wed, 2006-06-21 at 23:24 -0700, Panu Matilainen wrote:
>> On Thu, 22 Jun 2006, Ralf Corsepius wrote:
>>
>>> On Thu, 2006-06-22 at 04:58 +0200, Ralf Corsepius wrote:
>>>> On Thu, 2006-06-22 at 01:38 +0300, Panu Matilainen wrote:
>>>>> 0.5.15lorg3.2 is out for grabbing:
>>>>> http://apt-rpm.org/releases/apt-0.5.15lorg3.2.tar.bz2
>>>>
>>>> Well, ...
>>>>
>>>> you should have incremented the release number in configure.ac and
>>>> should have used "make dist" to cut the tarball.
>>
>> It was created with "make dist" - what makes you think otherwise?
>
>> From configure.ac svn(234):
>
> AC_INIT([apt],[0.5.15lorg3.1],[apt-rpm at lists.laiskiainen.org])
>
> => "make dist" would create an apt-0.5.15lorg3.1.tar.bz2 tarball

On the trunk, yes.

>>> The usual strategy to prevent this kind of issues to happen, is to
>>> increment the release number in SVN/CVS repo to (latest release+1)
>>> shortly after a release.
>>>
>>> Therefore, I am proposing the patch below.
>>
>> Next release based on trunk is more likely to be lorg4 (unless we decide
>> to do the name + versioning scheme change at that point as well) but yeah,
>> I'll bump the release in trunk as well.
> Are you using branches?

Yes, 3.2 is a highly conservative bugfix-only release from a separate 
branch. I thought that would've been obvious from the changelog.
Trunk has some ways to go before it's in releasable shape :)

 	- Panu -