[scribus-dev] What does “acknowledged” issue status mean?

Gregory Pittman gpittman at iglou.com
Sun Nov 1 19:52:03 UTC 2015

On 11/01/2015 05:14 AM, Khaled Hosny wrote:
> On Sun, Nov 01, 2015 at 08:35:14AM +0100, JLuc wrote:
>> ale has answered well but here are a few more precisions :
>> in the scribus community only few people are C++ developpers and have commit rights :
>> franz, MrB=Craig and jghali (and also avox when he is there).
>> In a bug report their voice should be more important for you to know
>> what features or code will possibly be merged.
> But asking for core contributors opinion before working on any issue is
> counter productive and decreases the usefulness of the bug tracker
> greatly. On the other hand working on some issue to found that the
> feature is deemed unacceptable is demotivating, such issues should not
> have been kept open in the first place.

Like any ad hoc system, it's hard to be always sensible and fair. One
reason for letting some feature request hang out there is to see if
others see the feature as useful. In general, it's not a good idea to
just start implemented requested features unless you know that there is
some consensus that it would be good to have. Sometimes a collection of
minor feature requests can be combined in some new collective feature.

Generally speaking fixing bugs is a good thing, provided they're
reproducible and produce something drastic like a crash.


More information about the scribus-dev mailing list