[Kde-imaging] Start working on next kipi release

[Colin Guthrie]

Tom Albers wrote:
>> If there needs to be a bugfix release we should create a branch of
>> /tags/0.1.2 called e.g. /branches/0.1.2a and commit changes in there.
>>
>> When done, the branch would then be svn cp'ed to a new tag and release
>> made. This could either become release 0.1.2a or release 0.1.3 (I'm
>> thinking that seeing as the next release is going to provide some ABI
>> incompatibilities, that we should at least increment the minor revision
>> number: e.g. 0.2)
> 
> Yes, i agree. Next release 0.2.0. Bugfixes of the burrent release should 
> become 0.1.3. Tags are indeed static and a branch will be setup when we need 
> a 0.1.3. I have not created that because that would cause confusion for 
> translaters and there is no need at this moment.

Indeed, you are right, there is no need to create the branch just now to 
avoid confusion and also because it may not be needed. Perhaps the next 
release will just be 0.2 and people will be happy with the current kipi 
until then :)

Col.