Bugs to be Buried

From Scribus Wiki
Revision as of 11:58, 23 May 2015 by FirasHanife (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Announcement: This page's function is for Scribus volunteers to post bugs that are possibly closed
Please adhere to the style of the page


In order to save time, we need to create a wiki page that is easy to read and understand for developers (their time is precious :) ).

Closing bugs

Bugs categorization

At the moment there are two main categories to fill with bug reports:

  1. Bugs to be closed: includes reports which are already implemented or fixed in the current releases such as 1.4 or 1.5.
  2. Bugs need information: includes reports which are "useless" in their current state as do not contain enough information to find and fix the issue or are simply related to very old Scribus versions. We may send a message to the reporter and, if there is no response, close them.

0. Bugs that need a verdict

1. Bugs to be closed

Note : there is a #tobeclosed tag in the bug tracker. See list of #tobeclosed bugs

Connect to [scribusbugs120plus_utf8] failed: Access denied for user 'mantis'@'www.scribus.net' to database 'scribusbugs120plus_utf8'

2. Bugs need information

Connect to [scribusbugs120plus_utf8] failed: Access denied for user 'mantis'@'www.scribus.net' to database 'scribusbugs120plus_utf8'