Bug 359960

Summary:	digiKam product category lacks recent release
Product:	[Applications] digikam	Reporter:	DrSlony <bugs>
Component:	Website	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	aspotashev, bugs, caulier.gilles, sheedy
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:	7.6.0

Description DrSlony 2016-03-01 16:54:49 UTC

The digiKam product's versions jump from 4.14.0 to 5.0.0. There is no 5.0.0 version yet, there are only betas, see https://www.digikam.org/about/releaseplan
There should also be a "digiKam 5 git" version entry, or something to that effect, which people can choose when reporting bugs.

Reproducible: Always

Comment 1 Ben Cooksley 2016-03-02 08:40:26 UTC

Users should not be requesting changes to the versions of a product on Bugzilla.
Such requests should come from the product maintainer.

Reassigning to Digikam for further feedback on what is necessary.

Comment 2 caulier.gilles 2016-03-02 08:55:15 UTC

5.0.0 beta versions need feedback from users who test. This is why 5.0.0 exists in bugzilla...

Gilles Caulier

Comment 3 Alexander Potashev 2016-03-03 08:49:09 UTC

I suggest that we add versions "5.0.0-beta1", "5.0.0-beta2", etc and move all exinsting bugs from version "5.0.0" to these new versions.

Comment 4 DrSlony 2016-03-03 12:27:45 UTC

"5.0.0 beta versions need feedback from users who test. This is why 5.0.0 exists in bugzilla..."
Maybe you did not understand the problem. There are two of them, allow me to explain:
1- There is no 5.0.0 version yet. If bugs which exist only in pre-5.0.0 versions, such as 5.0.0-beta3 for example, are filed as "5.0.0", then you will have a mess when 5.0.0 is released on 29 May 2016.
2- Some users, such as myself, get the latest code from git. If I find a bug I want it to be clear that this bug is in today's git version, not in some tag which is either many commits behind git, or as is the case with 5.0.0 not even released yet.