XoopsWiki - Core QA : XOOPS Project

XOOPS

Home XOOPS FAQ All about XOOPS XOOPS News Donations XOOPS Links Board of Advisors XOOPS Innovators XOOPSers Awards License Terms of Use Link to us Refer a friend WOX Newsletter

Lost Password?

Register now!

Support

Support Forums Forum New Posts International Support Facebook Group LinkedIn Group Delicious Links Flickr Images

Downloads

XOOPS Core Modules Module Packs Themes (old) Themes Gallery (beta) SVN Nightly Build

Documentation

Wiki FAQ Submit a Q&A Request a Q&A Open questions Demo API

Development

SourceForge dev.xoops.org Code SVN Report Bug Request Feature Submit Patch

Goals

to ensure quality of new releases (less bugs --> less support --> more contributions)
to ensure participation of community during the release process (more testers --> more assurance --> quicker release processes)

[edit]

Materials

[edit]

Release versioning

to be written

[edit]

General Naming Conventions

to be written

[edit]

Release Delays

in case of a bug fix release

A minimum of 1 week between RC and final have to be respected.

in case of a release that ads new features

A minimum of 2 weeks between RC and final have to be respected.
Generally, we will let users 2 weeks between two releases (beta, RC, or final) to test it

in case of a security fix release

For critical security fixes ==> those are released immediately.

[edit]

What to check before releasing?

- check if third party components have not been updated (for security purposes mainly)

PHPMailer http://phpmailer.codeworxtech.com/
Smarty http://smarty.php.net
Snoopy http://sourceforge.net/projects/snoopy/

- checksum md5 files have to be accurate
- release notes have been updated
- changelog is completed
- upgrade script has been updated
- upgrade readme is accurate
- indicate language changes (diff)

[edit]

What packages to release?

- upgrade package
- full package
for both in .zip / .tar files

[edit]

Where to announce the releases?

- xoops.org and SF news for final, sometimes for RC if needed
- xoops_announce ml for all releases

[edit]

Where to declare bugs ?

In the SF bugtracker, with details about your environment (php/mysql/browser), some explanations about how you get the error, the error message that appeared, and eventually the fix if you found it

[edit]

What minimum features to test in case of a new release?

First of all, please activate the php debug panel, and report any message

- install from scratch
- upgrade from the last 2 previous releases, from a website that already has data and modules in its database
- subscription of a new user
- install of 2 basic modules (eg news and CBB)
- uninstall of 2 basic modules (eg news and CBB)
- correct use of 2 basic modules (eg news and CBB)
- group management
- notifications
- PM
- user profil edit+save - password change

[edit]