[scribus] Request to all bug testers and potential reporters

Kunda Loves Scribus scribus.user at gmail.com
Wed Aug 6 13:58:10 UTC 2014

Hi everybody,

This is an unofficial request.

1.5.0 release is just around the corner due to a decision that the roadmap
(on the bugtracker) be limited strictly for crash bugs. The idea is that
the next dev release version occur as soon and as stable as possible.

So the request here is that if you've noticed some unstable 1.5.0svn
activity that leads to a crash, please attempt to examine it better so that
you can reproduce the steps and report on Mantis. If you've been postponing
to post a bug because you haven't had the time for it, now would be a good
time to make the time for it.

A great example of a succinct and thorough bug report would be
http://bugs.scribus.net/view.php?id=12477 (props to FirasH, bug reporter
extraordinaire). Clear step-by-step instructions with an attached gdb stack
trace (the stack trace is optional, though highly preferred because it
helps facilitate a solution faster).

Please also check to see if the issue you encounter has been reported
already before you report. If so, please notate the issue that exists with
feedback that you can reproduce on the platform/distro version and Scribus
version + revision #

FYI, please compile 1.5svn from HEAD to do the testing. There are several
guides out there to help with doing that for certain platforms and distros.
If you need help please make yourself heard on IRC or here.  If you can
offer any patches please be forthcoming with them, though remember that it
takes work for the devs to examine patches so create them per scribus
coding-style requirements.

Thanks again for your participation and attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20140806/c19c764b/attachment.html>

More information about the scribus mailing list