KDE Stable Testers
1.
Project Description
Packages that are marked for stabilisation usually have to pass a series of tests.
Unfortunately these tests are hard to apply to the mass stabilization process
like kde that includes ~300 packages. This subproject will help to find possible
issues in the testing versions of kde-/* packages.
Every month the KDE team have a meeting. In that meeting
the members decide if there will be a new stable candidate.
If there is such, a member of the KDE team will create the full list of
packages that are going to be stabilized, open the STABLEREQ on our bugzilla and
CC the kde-stable alias. Now all testers can start their tests.
2.
Project Goal
Take advantage of the testing that comes from the daily use.
3.
Requirements
To join this team there are no quizzes required. Members don't need
to be developers, but they need to use KDE on a daily basis and run a stable environment
with only the requested KDE version keyworded as testing.
4.
What to do
The testing procedure is simple. Every member should simply install, when asked, the unstable version of KDE that we have in the main tree.
If there are bugs found. It needs to be verified if it is a local fault, a packaging bug, or an upstream bug. So please consult a member
of the KDE team that will guide you. A contact via IRC is preferable.
5.
What you get
Once you have joined the team, your mail will be added to the kde-stable alias;
this means that you will receive all mails sent to kde-stable@gentoo.org.
You will receive voice (+v) in #gentoo-kde on irc.freenode.net.
6.
Members
| Full Name |
Nickname |
Arch |
Email |
Role |
| Agostino Sarubbo |
ago |
amd64/ppc/x86 |
ago@gentoo.org |
Lead |
| Chris Reffett |
creffett |
amd64 |
creffett@gentoo.org |
Lead |
| Richard Yao |
ryao |
amd64 |
ryao@gentoo.org |
Member |
| Vicente Olivert Riera |
vincent |
ppc |
vincent@gentoo.org |
Member |
| Enrico Tagliavini |
[Enrico] |
amd64 |
enrico.tagliavini@gmail.com |
Member |
| Aaron Bauman |
B-Man |
amd64 |
bmangentoo@gmail.com |
Member |
| Michael Mair-Keimberger |
iamnr3 |
amd64 |
bu9zilla@gmail.com |
Member |
| Jim Sublette |
jsubl2 |
amd64 |
jim.sublette@gmail.com |
Member |
| Maurizio Camisaschi |
k01 |
amd64 |
k01@live.it |
Member |
| Paul Healy |
lmiphay |
amd64 |
lmiphay@gmail.com |
Member |
| Nick Pershyn |
oquol |
amd64 |
nikolay.pershyn@gmail.com |
Member |
| Denis Mitov |
Phr33d0m |
amd64 |
god@politeia.in |
Member |
| Jagath Samarabandu |
Sam |
amd64 |
jagath@uwo.ca |
Member |
| Mikle Kolyada |
zlogene |
amd64/x86 |
zlog.gentoo@gmail.com |
Member |
7.
Participating
In order to become part of the team you need to observe these requirements:
- Use a safe set of CFLAGS/CXXFLAGS, example: CFLAGS="-march=native -O2"
- Add --hash-style=gnu to your LDFLAGS in that manner: LDFLAGS="${LDFLAGS} -Wl,--hash-style=gnu"
- Add some FEATURES in that manner: FEATURES="${FEATURES} collision-protect multilib-strict sandbox userpriv usersandbox"
You need to set multilib-strict only if you are using an amd64 system. Pay attention if
you are using --keep-going. For question and join please contact only the leads via email.
The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply.
|