5,576
edits
Changes
From SME Server
Jump to navigationJump to search→Verifying Bugs
===Verifying Bugs===
===Verifying Bugs===
Bugs in the SME Server Release, SME Contribs & SME Server Translations products
Bugs in the SME Server Release, SME Contribs & SME Server Translations products
need to be verified when fixed, see the [[Verification_Queue]] for the current list.
need to be verified when fixed, see the [[Verification_Queue]] for the current list. See [[SME_Server:Documentation:QA:Verification]] for a detailed description of the verification process. <br />
An example is [[bugzilla:3727]] or [[bugzilla:7364]].
An example is [[bugzilla:3727]] or [[bugzilla:7364]].
Other Products can be Closed after being fixed, as they are not part of the updates process.
Other Products can be Closed after being fixed, as they are not part of the updates process.
The bug report will detail the exact package and version needed. These are normally in smeupdates-testing and can be installed by yum, for example
The bug report will detail the exact package and version needed. These are normally in smeupdates-testing and can be installed by :
yum --enablerepo=smeupdates-testing update <package>
for example
yum --enablerepo=smeupdates-testing update e-smith-ldap
As it is a manual step to move packages into smeupdates-testing the most recent packages will be in smetest and can be installed from there if necessary.
for example
yum --enablerepo=smetest update e-smith-ldap
or if you need several repositories :
yum --enablerepo=smetest,smeupdates-testing,smedev update e-smith-ldap
When performing verification, please use the following template:
When performing verification, please use the following template:
'''VERIFICATION TEMPLATE'''
'''VERIFICATION TEMPLATE'''
= ENVIRONMENT: [eg: sme 8.0 64 bits clean from CD + all updates]
= ENVIRONMENT:
= ORIGINAL PROBLEM:
= RESOLUTION:
= CURRENT VERSION INSTALLED:
= TESTING:
= ~]# /sbin/e-smith/audittools/newrpms [Provide this if customised]
= UPDATED VERSION INSTALLED:
= PROBLEM FIXED:
= VERIFIED OR REOPEN:
= DOCUMENTATION IMPACT:
= SUGGESTED RELEASE NOTES:
AS AN EXAMPLE:
VERIFICATION
= ENVIRONMENT:
[description of test system (version, installation methods, upgrade history. etc).
If you have some non-core package installed, run /sbin/e-smith/audittools/newrpms and provide output]
= ORIGINAL PROBLEM:
= ORIGINAL PROBLEM:
[Description of problem]
[Summarise bug]
= RESOLUTION:
= RESOLUTION:
[Reprint changelogs of new package being verified
[Insert changelog for new package]
In example:
Fixed in e-smith-base
* Mon Apr 21 2013 chris burnat <devlist@burnat.com> 5.4.0-27.sme
- Fix the way '.' works in bash [SME: 7532]
= CURRENT VERSION INSTALLED:
= CURRENT VERSION INSTALLED:
[rpm -q]
[rpm -qa <package name>]
=TESTING:
=TESTING:
[Show in detail existing problem being fixed by new package]
[Reproduce bug if you can, showing steps taken]
= UPDATED VERSION INSTALLED:
= UPDATED VERSION INSTALLED:
[Show installation of new package]
[Update to new package, show steps taken]
and:
[rpm -qa <package name>]
= PROBLEM FIXED?:
[Repeat steps carried out under TESTING above.
= PROBLEM FIXED:
[Repeat testing after applying new package]
= VERIFIED OR REOPEN:
= VERIFIED OR REOPEN:
[Conclusion based on testing above - fixed/not fixed]
[Problem fixed, then VERIFIED - not fixed, then REOPEN]
Note: if you may not have rights to toggle resolution, someone will do it for you
= DOCUMENTATION IMPACT:
= DOCUMENTATION IMPACT:
[Eg: is a DB variable created/removed?]
[Does something need documentation, eg a db or new procedure? if affirmative, please provide details, someone will later punt to docteam for action]
= SUGGESTED RELEASE NOTES:
= SUGGESTED RELEASE NOTES:
[Summary of what has been fixed in new package]
[Summary of what was fixed]
===Testing===
===Testing===
Set the flag to ? to say someone needs to look at it
Set the flag to ? to say someone needs to look at it
[[Category:SME Server]][[Category:SME9-Development]]
[[Category:SME Server]][[Category:SME9-Development]][[Category:Developer]]
