Bugs to be Buried: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(Some changes to the layout)
m (MInor corrections)
Line 3: Line 3:


== 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 :) ).




== Bugs categorization ==
== Bugs categorization ==
At the moment there are two main categories to fill with bugs reports:
At the moment there are two main categories to fill with bug reports:
# Bugs to be closed: includes reports which are already implemented in the current releases such as 1.4 or 1.5
# Bugs to be closed: includes reports which are already implemented in the current releases such as 1.4 or 1.5.
# Bugs need information: includes reports which are "useless" in their current state as in there isn't enough information. We may send a message to the reporter and, if there is no response, should be closed after a determined period of time (to be defined)
# Bugs need information: includes reports which are "useless" in their current state as do not contain enough information to find and fix the issue. We may send a message to the reporter and, if there is no response, should closed them after a determined period of time (to be defined).




=== 1. Bugs to be closed ===
=== 1. Bugs to be closed ===
{| class="wikitable"
{| class="wikitable"
!'''Bug #'''  
!'''Bug #'''  
Line 26: Line 25:


=== 2. Bugs need information ===
=== 2. Bugs need information ===
{| class="wikitable"
{| class="wikitable"
!'''Bug #'''  
!'''Bug #'''  

Revision as of 22:31, 23 June 2014

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 :) ).


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 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. We may send a message to the reporter and, if there is no response, should closed them after a determined period of time (to be defined).


1. Bugs to be closed

Bug # Description Reason
1069 Auto-adjust size of text box to the text Already implemented in 1.5.0.svn with "Adjust Frame Height to Text"
####


2. Bugs need information

Bug # Description Reason
####
####