Changes

From SME Server
Jump to navigationJump to search

SME Server:Documentation:QA:Verification (view source)

Revision as of 00:36, 4 March 2013

152 bytes removed ,  00:36, 4 March 2013
m
Reverted edits by Trex (talk) to last revision by Uniqsys
Line 19: Line 19:     
  = Environment:
 
  = Environment:
−
 
+
 +
= Current version installed:
 +
 
  = Original problem:
 
  = Original problem:
−
 
+
 
  = Resolution:
 
  = Resolution:
−
 
+
   
−
  = Current version installed:
  −
 
  −
= Testing
  −
 
   
  = Updated version installed:
 
  = Updated version installed:
−
 
+
 
  = Problem fixed:
 
  = Problem fixed:
−
 
+
 +
= Release note information suggestion:
 +
 
  = Verified or Reopen:
 
  = Verified or Reopen:
−
  −
= Documentation Impact:
  −
  −
= Suggested Release Notes:
      
====Environment====
 
====Environment====
Line 42: Line 38:     
  SME Server 7.5 fully updated, no contribs installed
 
  SME Server 7.5 fully updated, no contribs installed
−
  −
====Original problem====
  −
This section is used to show that you can reproduce the original problem on your test machine. It is important that you do this as accurate and methodological as possible as you will have to reproduce these steps after you have updated to the newer pacakage(s) to show that the problem is actually fixed.
  −
Make sure to make your test as extensive as required but on the other hand try and keep things as clear and dense as possible.
  −
{{{Note box|In the case of New Feature Requests (NFR) or if a previous version of the package with the reported bug is not available this step might be skipped.}}}
  −
  −
====Resolution====
  −
This section is used to shortly describe which steps need to be taken in order to upgrade to the fixed version, usually it will be something like this:
  −
  −
Install package1 and package2 from smeupdates-testing and/or smetest
  −
  −
After that it is time to actually upgrade to the new package(s).
      
====Current version installed====
 
====Current version installed====
Line 68: Line 52:  
  [root@smetest ~]#
 
  [root@smetest ~]#
   −
====Testing====
+
====Original problem====
−
Show in detail existing problem being fixed by new package
+
This section is used to show that you can reproduce the original problem on your test machine. It is important that you do this as accurate and methodological as possible as you will have to reproduce these steps after you have updated to the newer pacakage(s) to show that the problem is actually fixed.
 +
Make sure to make your test as extensive as required but on the other hand try and keep things as clear and dense as possible.
 +
{{{Note box|In the case of New Feature Requests (NFR) or if a previous version of the package with the reported bug is not available this step might be skipped.}}}
 +
 
 +
====Resolution====
 +
This section is used to shortly describe which steps need to be taken in order to upgrade to the fixed version, usually it will be something like this:
 +
 
 +
Install package1 and package2 from smeupdates-testing and/or smetest
 +
 
 +
After that it is time to actually upgrade to the new package(s).
    
====Updated version installed====
 
====Updated version installed====
Line 78: Line 71:  
Be sure to check that not only the problem is fixed, but also make sure no error messages are found in the logfiles or on the console when entering the comments. If errors are present please report them to the bug report if it affects the fix, or open a new bug when a new issue is discovered.
 
Be sure to check that not only the problem is fixed, but also make sure no error messages are found in the logfiles or on the console when entering the comments. If errors are present please report them to the bug report if it affects the fix, or open a new bug when a new issue is discovered.
 
Also make sure to test normal functionality related to the changes are still working properly.
 
Also make sure to test normal functionality related to the changes are still working properly.
 +
 +
====Release note information suggestion====
 +
If you feel capable please suggest the information we can put in the release notes in one or two lines, if you cannot please leave this empty, or for instance specify it is to be determined by specifying ''T. B. D.''.
    
====Verified or Reopen====
 
====Verified or Reopen====
Line 83: Line 79:  
When REOPENING the bug, please motivate this briefly.
 
When REOPENING the bug, please motivate this briefly.
 
{{Note box|Please, do not forget to also set the status field, at the bottom of the comment field, to the proper value matching your conclusion.}}
 
{{Note box|Please, do not forget to also set the status field, at the bottom of the comment field, to the proper value matching your conclusion.}}
−
  −
====Documentation Impact====
  −
Eg: is a DB variable created/removed?
  −
  −
====Suggested release notes====
  −
If you feel capable please suggest the information we can put in the release notes in one or two lines, if you cannot please leave this empty, or for instance specify it is to be determined by specifying ''T. B. D.''.
 
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/19387"

Navigation menu