Testers! It’s that time again!
Parrot 4.6 is almost ready, and we need testers!
What are we looking for?
Please report to us what works and what needs to be fixed before the final release.
This is not the proper place where to post your ideas and tips. Use the Parrot 4.6 Development Discussions topic to discuss opinions and ideas.
For the beta testers:
Things that need to be tested
Parrot Home live
Parrot Security live
Parrot Home KDE live
All of the images in both standard and uncommon configurations (except of course, don’t report configurations errors that are not meant to work on Debian).
How to report bugs
Please write up a report (an example has been posted below) that lists the result of all your tests, and reports both working and broken apps or entities, and end with suggestions on how to solve issues (if a solution is known by the tester).
Please ensure your bug is reproducible, if not please have your logs available.
Please post your report as a comment to this topic.
If there is a problem which merits a confidential report, you may email your report to palinuro AT parrotsec DOT org or team AT parrotsec DOT org, but we strongly prefer comments to be public.
For Firejail errors please use firejail’s extensive debugging suite (see firejail’s manpage or their docs for more info)
Please check your logs and post them with your report, if you can, for the errors
What a beta tester should not do
Parrot OS is not a piece of software, it is a whole operating system. An operating system, by definition, is a collection of many many system components and completely independent programs that we don’t develop.
We don’t want the individual parrot programs to be extensively audited, we need our beta testers to use the system in real life scenarios and spot usability issues, crashes and unexpected behaviors (though if you are interested in doing so please send @s1udge a PM).
Reports released after the final stable release may not be taken in consideration, but if you spot something important, we may decide to schedule a new emergency release that addresses critical bugs. We consider these cases as exceptions, as latecomers are usually ignored.
If a ParrotOS bug is caused by a bug from software which is not maintained by Parrot Developers, that bug should be reported to the appropriate program developers, and not to Parrot Developers (i.e. firefox, MATE or libreoffice).
Brief comments are not full reports. Please do not comment to this topic if you don’t have a complete report. So please, help us keep this topic as clean as possible. To discuss bugs and issues specific to the beta testing please discuss at ParrotOS 4.6 QA/Testing Discussion.
Tests done on older versions of the system make no sense for us, as the purpose of this beta testing program is to spot issues on the ISO files for Parrot 4.6 that the Parrot Team proposes during the beta testing phase.