On 12/17/20 8:44 AM, Neal Gompa wrote:
On Tue, Dec 15, 2020 at 1:56 PM Stefan Seyfried
wrote: On 14.12.20 01:04, Simon Lees wrote:
As a broader question to the community do we need such a list for tumbleweed announcements and reports of major breakages? The answer we got last time was no.
Because the canary "lots of answers to a tumbleweed announcement? => better be careful" works very well without another list.
I also cannot even find a factory-support list at all?
In my opinion, the factory@ mailing list is a poorly named one. It's pretty clear from how people respond to folks asking questions about Tumbleweed that it's purely a "development" list.
It is also pretty clear that factory@ isn't just about Factory development, but pretty much *all* development of the openSUSE Linux distributions (since we do talk about openSUSE Leap here too), and it would be more appropriate to rename it to devel@.
This was discussed in the past but didn't have strong support in the community because in openSUSE Factory has always equaled devel.
To me, I think it would make sense to have devel-announce@ for the announcement emails, but the issue with that is that we rely on users replying to those emails on-list to get feedback about specific issues with those snapshots, hence why they are sent to factory@ today (and would be sent to devel@ if we renamed this list). On the other hand, having a devel-announce@ list would make it possible for folks to subscribe to *just* those emails in a read-only manner.
I also don't think an announce is the right answer either, but maybe moving to having a devel- for all development discussion and a tumbleweed list to cover announcements and reports of issues (with accompanying bug report because I wouldn't expect all maintainers to subscribe.) might be the way to go. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B