On 2014-03-31 22:42, Rahul Sundaram wrote:
Hi
On Mon, Mar 31, 2014 at 11:24 PM, Robin Laing wrote:
When a feature that is used is broken, even to the point an application
crashes, and the fix requires the new version, then it is in issue in the
usability of Fedora. This has been my biggest complaint over the years. I
am finding this with some applications on F20 that I have used in the past.
In some cases, it isn't even a full version update but a 0.1 update that
is refused.
Did you file any bug report? Example? In any case, changing the update
policy is not going to fix this. There is nothing in the update policy
that prevents a maintainer from pushing a point release that fixes a bug.
It could be resource shortage issue but a policy will never force volunteer
maintainers. It can only set guidelines that communicate expectations.
Rahul
There is a bug reported and the automatic reporting tool keeps telling
me it is reported. I would have to look again but I think the issue is
upstream and how they handle a new library.
In F19, the one application, the maintainer points to the policy of not
move to a new major release.
I will live with it.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
