Bugs to be Buried: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(Some changes to the layout)
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}}


== Guidelines ==
== Guidelines ==
# Already present in 1.4 or 1.5
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 :) )
# 'Useless' as in there isn't enough information (send a message to the reporter and maybe after a month without response close it)
 
 
== Bugs categorization ==
At the moment there are two main categories to fill with bugs reports:
# 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 proposed to be closed ==
 
=== 1. Bugs to be closed ===


{| class="wikitable"
{| class="wikitable"
Line 13: Line 20:
|-
|-
|{{b|1069}} || Auto-adjust size of text box to the text || Already implemented in 1.5.0.svn with "Adjust Frame Height to Text"
|{{b|1069}} || Auto-adjust size of text box to the text || Already implemented in 1.5.0.svn with "Adjust Frame Height to Text"
|-
|{{b|####}} || ||
|}
=== 2. Bugs need information ===
{| class="wikitable"
!'''Bug #'''
! '''Description'''
! '''Reason'''
|-
|{{b|####}} || ||
|-
|-
|{{b|####}} || ||
|{{b|####}} || ||

Revision as of 22:27, 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 bugs 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 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)


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
####
####