I'm wondering if there are more people who might be interested in release candidate testing of the browser to catch potential issues before publication.
At the moment we're having a small group of core community members who can do this, but if there's interest, I could expand it with people with specific interest.
A few important things in that case:
Sooo... let me know what you think?
At the moment we're having a small group of core community members who can do this, but if there's interest, I could expand it with people with specific interest.
A few important things in that case:
- This isn't just "early access" or an unstable build. It's only a few days before each release and is meant to catch anything critical in final builds before they go live. This won't be for on-going development issues or stuff that's not directly related to the release.
- Even though builds tested are "release-ready" builds, they are not necessarily final and should never be disseminated to others. This is an absolute critical condition for participating in release candidate testing. If you don't think you can adhere to this hard rule, don't apply. We want to avoid RC binaries floating around as "release" that might have issues.
- Technical expertise and/or long-term use of Pale Moon is pretty much a prerequisite.
- Backups of your profile are essential.
- We'd be looking for people on different operating systems we directly build for: Windows 7-11, Linux GTK2 and GTK3, MacOS and FreeBSD.
- Fairly broad testing would be beneficial, specifically around the areas of the preliminary release notes that come with release candidates.
Sooo... let me know what you think?