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 | |
Sentry Crash Report: |
Description
DrSlony
2016-03-01 16:54:49 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. 5.0.0 beta versions need feedback from users who test. This is why 5.0.0 exists in bugzilla... Gilles Caulier 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. "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. |