Difference between revisions of "Bugs to be Buried"

From Scribus Wiki
Jump to: navigation, search
m
(added 4883, 4885)
Line 1: Line 1:
 
{{Announcement|This page's function is for Scribus volunteers to post bugs that are possibly closed|Please adhere to the style of the page}}
 
{{Announcement|This page's function is for Scribus volunteers to post bugs that are possibly closed|Please adhere to the style of the page}}
 
+
__NOTOC__
 
 
 
== Guidelines ==
 
== 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 :) ).
 
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====
 
====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 ==
 
== Bugs categorization ==
 
At the moment there are two main categories to fill with bug reports:
 
At the moment there are two main categories to fill with bug reports:
Line 51: Line 43:
  
 
<mantis>
 
<mantis>
bugid = 393,2568,2583,2421,3096,3822,5283,6079,6205,7147,8254,9159,9169,9296,9365,10265,11361,11447,11605,11624,
+
bugid = 393,2568,2583,2421,3096,3822,4883,4885,5283,6079,6205,7147,8254,9159,9169,9296,9365,10265,11361,11447,11605,11624,
 
header = true
 
header = true
 
color = true
 
color = true
Line 58: Line 50:
 
comment#3096 = Updated! Bug still exists in certain conditions
 
comment#3096 = Updated! Bug still exists in certain conditions
 
comment#3822 = Should be reproduced or closed
 
comment#3822 = Should be reproduced or closed
 +
comment#4883 =
 +
comment#4885 =
 
comment#9296 = Can someone reproduce this?
 
comment#9296 = Can someone reproduce this?
 
comment#10265 = No steps or files to reproduce with (Updated:12-Feb-07)
 
comment#10265 = No steps or files to reproduce with (Updated:12-Feb-07)

Revision as of 13:43, 16 May 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

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'


Related