https://bugzilla.suse.com/show_bug.cgi?id=1192457 https://bugzilla.suse.com/show_bug.cgi?id=1192457#c16 --- Comment #16 from Martin Wilck <martin.wilck@suse.com> --- (Copied this from https://jira.suse.com/browse/PM-2971 for information - I think further discussion should happen there, or possibly on the kernel ML, rather than on BZ). Let me ask again how we are supposed to proceed now. In my understanding, the existence of this "Sould have" Jira ticket implies that engineering got an order from PM for the implementation this feature. So we should try. Trying implies exposing the feature to a larger audience for testing and finding possible rough edges. Everyone understands that if unsurmountable problems occur, the project fails. But what happened here is that we pulled back on the first occurence of an issue. The side effect of this is that real-world testing effectively doesn't happen any more. So possible other issues will not be found, and the known ones will be harder to solve. It was expected that some issues would occur. It was known beforehand that package size would increase. Therefore if we want to have this feature, we need to deal with that and free the required space on the media. That's difficult, and it might mean that live image creation fails for a certain period of time. And this is what happens with "factory first" - effectively we beta-test on a distribution that others use in production. It's not the first time something breaks in factory, and not a unique incident by any means. By pulling back and switching to xz for both Factory and SP4 at this point in time, we basically give up the chance to "test if fully on TW first" as Takashi said above. That puts the implementation of this feature for SP4 at high risk. I don't want to push this feature forcibly. If there are strong reasons not to implement it, I won't insist. But I believe this pull-back was premature. -- You are receiving this mail because: You are the assignee for the bug.