On 28/05/18 22:08, Stefan Seyfried wrote:
Hi Simon,
On 28.05.2018 13:51, Simon Lees wrote:
The board hopes that with the changes outlined above the contents of the opensuse-factory@o.o will go back to just being general distro development discussion so if your post to openSUSE factory is something other then that think twice about where the more appropriate place to post is.
Actually the posts "foo seems broken for me after $DATE snapshot" are the most useful content for me on factory@
Now I am supposed to scan bugzilla for problems before "zypper dup"? To quote an almost famous SUSE employee: "Kein f*ckender Weg!" ;-) (sorry, the joke works only in german)
The new tumbleweed snapshots will continue to be posted to factory but we would ask you do not reply to them in order to report issues / bugs. If a bug is reported that a package maintainer believes will cause significant issues for most tumbleweed users ie not being able to boot / login or severe data loss we still invite the maintainer to post a warning to opensuse-factory but such issues happen very rarely and as such we don't expect to see many such posts.
This will make opensuse-factory "mostly useless" for me and I will probably stop reading it on a regular base. I will not subscribe to a "-support" list.
As I had pointed out to a board member in person in Prague already, the current style of opensuse-factory worked just fine for me (maybe drop the flamewars).
If opensuse-factory is ever returned to its current modus operandi, then please someone ping me, so I might start reading it agin.
P.S.: I would be slightly interested in a description of the problem this change is supposed to solve...
The main issue that this is meant to solve is that many of the people working on openSUSE development have stopped paying as much attention to the factory mailing list because it is full of foo is broken in tumbleweed posts and they don't care about those. The board did discuss creating a separate mailing list for the use case you described to be used with both tumbleweed and leap beta's but we decided against it for now. This could be added in the future if its useful for people but we wanted to see how the current changes worked out first. One of the issues is posting "foo is broken" to a mailing list doesn't mean that the right people will notice the post and fix the issue so if we were to create such a list I think it would need a rule along the lines of you can only post that something is broken once you have already created a bug ticket for it. Again this is something the board decided it didn't want to do right now but would be very open to changing its mind on into the future should there be sufficient community demand for it. -- 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