Andreas: You are right. There's an opportunity here. I wonder about enabling people with limited time, but deep, narrow package interest to help vet what they care about and provide those facts for the rest of us. I'd have done this myself several times, if I knew a distro-way to do it. What if it were easy for Carlos to propagate his observation that "here be regressions" around tbird? Our other colleague would not have been so surprised.
We probably should have made this more clear in the maintenance update descriptive text
I wonder if there isn't a broader "we" to leverage, if we could find a way for computer-literate users, doing something *using* OpenSuSE to contribute we'd get a lot more leverage on regressions and surprises. I'm feeling like a tad more support and guidance could get us a lot. Release candidates seems a likely time: "Check these out and put your results here, by chunk, then we'll all know." Not a "keep out" participation gate, but an invitation & guidance to help people contribute helpfully. We could use a better way to propogate what Carlos knew: T-Bird works pretty well; there are some regressions re: plug-ins, with work-arounds, YMMV.
Ultimately it is something that we are willing to accept from a security maintenance standpoint. 60 is the current ESR for
I suspect we'd knock down a lot of noise around inclusion / upgrade decisions, if the consequences were a bit easier to see for people who use the decisions, vs. monitor the lists & etc. all the time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org