On Tue, 12 Jul 2016 12:52:49 +0200, Dominique Leuenberger / DimStar wrote:
On Tue, 2016-07-12 at 12:42 +0200, Takashi Iwai wrote:
Hi Ludwig,
when a Leap 42.2 package is "forked" to take a TW package, does it automatically follow the later TW package update as well until the 42.2 code freeze? Or do we need to resubmit to 42.2 at each time?
Hi Takashi,
Allow me to reply to this message while Ludwig is enjoying some time off.
Packages that are marked to be coming from TW are NOT automatically updated based on TW. Despite the 'promise' that TW is supposedly stable, there are always smaller / bigger packages that are a bit 'too bleedy' to be considered for a real LTS product, such as Leap.
For this reason, packages that have source openSUSE:Factory do require explicit action from the package maintainers.
Thanks, now it's clear. I asked it because the policy was a bit different at the time of 42.1. At that time, the TW package update was tracked until 42.1 went to the code freeze. But then I guess we'd need a manual review for such forked packages some time later before RC, so that we catch any overlooked package updates / fixes. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org