Do we have a check list to help developers/packagers watch for QA problems with packages? I have not seen any. How about we start one?
1. Check two apps in each menu category of the T-Menu to verify the Help file handbook is available.
2. Run a system test looking for broken sym links. (I use a short script I can share.)
3. Do all apps in the T-Menu start?
4. Check the xsession logs for unexpected or unusual errors and messages.
5. Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
On Mon, Nov 28, 2011 at 16:29, Darrell Anderson humanreadable@yahoo.com wrote:
Do we have a check list to help developers/packagers watch for QA problems with packages? I have not seen any. How about we start one?
Check two apps in each menu category of the T-Menu to verify the Help file handbook is available.
Run a system test looking for broken sym links. (I use a short script I can share.)
Do all apps in the T-Menu start?
Check the xsession logs for unexpected or unusual errors and messages.
Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
We used to have a list like that; I have absolutely no idea where it went. Check the wiki... I might have copied the list there.
On 28 November 2011 16:52, Robert Xu robxu9@gmail.com wrote:
On Mon, Nov 28, 2011 at 16:29, Darrell Anderson humanreadable@yahoo.com wrote:
Do we have a check list to help developers/packagers watch for QA
problems with packages? I have not seen any. How about we start one?
- Check two apps in each menu category of the T-Menu to verify the Help
file handbook is available.
- Run a system test looking for broken sym links. (I use a short script
I can share.)
Do all apps in the T-Menu start?
Check the xsession logs for unexpected or unusual errors and messages.
Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
We used to have a list like that; I have absolutely no idea where it went. Check the wiki... I might have copied the list there.
I think it went up in smoke with the beta phase etherpad
Calvin
Seems a fine start. Can you post it on the wiki?
Best regards, Tiago
On Mon, Nov 28, 2011 at 9:29 PM, Darrell Anderson humanreadable@yahoo.comwrote:
Do we have a check list to help developers/packagers watch for QA problems with packages? I have not seen any. How about we start one?
- Check two apps in each menu category of the T-Menu to verify the Help
file handbook is available.
- Run a system test looking for broken sym links. (I use a short script I
can share.)
Do all apps in the T-Menu start?
Check the xsession logs for unexpected or unusual errors and messages.
Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Seems a fine start. Can you post it on the wiki?
Done.
http://www.trinitydesktop.org/wiki/bin/view/Developers/PackageBuildQA
Parent page: http://www.trinitydesktop.org/wiki/bin/view/Developers/WebHome
Everybody please help improve this check list. :)
Darrell
-
Calvin Morrison -
Darrell Anderson -
Robert Xu -
Tiago Marques