I’d like to start contributing to the testing phase, but I’m not sure where to go. I currently have Rome Plasma6 x86_64 installed on my laptop. The pace and possible instability of Cooker does not scare me, but I want to go where the help is most needed.
So, question for the long-time crew. What needs more eyes on it, cooker or rome with testing repos? Either way I will be on a baremetal install on my laptop.
If you see a lot of things being built, review them and see if any fit your test case, especially any DE’s, WM’s, or graphics servers. When in doubt, ask in the cooker chat if there is a major rebuild or upgrade happening to critical components. If you do that, Cooker is rock solid. As I have stated to others, I have only ever broke Cooker when I wasn’t paying attention to what is happening, and even then it was just broken to the terminal. I also tend to do that frequently both because I have a short attention span, and because I love suffering for you people so we can make OM great.
I use the checklists as a guide for what to test, I do not send them anywhere because I doubt we have anyone with time to read them and follow through.
Then I report issues in IRC (OM-Chat), or file a bug report. Sometimes when devs are working on something we also need to tell them it works. For example I know that right now a couple of them are working on things with Wayland and our Spins.
For users this keeps things simple but the more different users and hardware tested on the better (betterer) we can make things,
To add to what I have written to test what is going to be in ROME next you would test in latest (dsynced) Cooker. The most recent Cooker isos are linked here.
To test what is going to be in Rock next you would test is latest (dsynced) ROME. The most recent ROME isos are here. Look in the container to be sure you are getting the most recent iso, we try to keep the individual numbered isos up to date but we also get busy at times and that updating gets delayed.