Difference between revisions of "Bugs to be Buried"

From Scribus Wiki
Jump to: navigation, search
Line 18: Line 18:
 
# 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.
 
# 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 ===
 +
<mantis>
 +
bugid = 2560, 12742,
 +
header = true
 +
color = true
 +
show  = id, category, priority, created, updated, summary
 +
comment#2560 = This is about the annoying aspect of assigning shortcuts in translations
 +
comment#12742 = QMessagebox issue remains
 +
comment# =
 +
comment# =
 +
comment# =
 +
</mantis>
  
 
=== 1. Bugs to be closed ===
 
=== 1. Bugs to be closed ===

Revision as of 00:29, 30 January 2015

Announcement: This page's function is for Scribus volunteers to post bugs that are possibly closed
Please adhere to the style of the page


Guidelines

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

Mostly questions ATM :

  • Who has the authorization to close bugs on the bug tracker ?
  • Could somebody else get that authorization to close bugs ?
  • What procedure should be followed so as to enable to close a specific bug without loosing valuable data ?

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

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


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'