[arch-general] Why is qtcreator updated to 3.0.1.git then 3.1.0beta1?
I noticed recently that qtcreator is updated to such non-stable versions, and there is no critical bug related that require such updates on the bug tracker. What is the reason this package is updated to such versions so early? I remember there used to be similar early updates with earlier versions of this package. Is it just the maintainer gets too excited?
On Fri, Mar 14, 2014 at 6:14 AM, GSC <xgdgsc@gmail.com> wrote:
I noticed recently that qtcreator is updated to such non-stable versions, and there is no critical bug related that require such updates on the bug tracker. What is the reason this package is updated to such versions so early? I remember there used to be similar early updates with earlier versions of this package. Is it just the maintainer gets too excited?
On 03/14/2014 02:35 PM, Karol Blazewicz wrote:
https://bugs.archlinux.org/task/39070 ? Thanks for the info. That' s the reason. Do we have any policy regarding updating package to an officially unstable version to provide bug fixes? What the severity should that bug be to make such an update?
On 14/03/14 03:10 AM, GSC wrote:
On 03/14/2014 02:35 PM, Karol Blazewicz wrote:
https://bugs.archlinux.org/task/39070 ? Thanks for the info. That' s the reason. Do we have any policy regarding updating package to an officially unstable version to provide bug fixes? What the severity should that bug be to make such an update?
If the projects don't actually plan on doing more point releases for the stable release, then it's not really a stable release at all. For example, LLVM releases *zero* fixes for a 'stable' release at the moment.
participants (3)
-
Daniel Micay
-
GSC
-
Karol Blazewicz