Dne 4.10.2016 v 14:11 Josef Reidinger napsal(a): > On Tue, 4 Oct 2016 13:58:30 +0200 > Ancor Gonzalez Sosa <[email protected]> wrote: >> And next question is, what will be release through self-update? >> Everything from the merge_after_release branches will be published in >> the self-update repo? Just asking, I don't see a reason to not do it.
That's actually a good question how to handle the self-update fixes. I guess that testing the self-update patches will be quite difficult (think about all test cases like autoinstallation/autoupgrade...). On the other hand IIRC some openQA tests already include the self update. That should help a bit. My assumption is that we should not release every SP2 update also as a self-update fix as building and testing is not trivial. But it actually depends on the QA and the maintenance teams how much work they can reserve for the self-updates. >> For example, I already have a trivial fix for this yast-bootloader bug >> https://bugzilla.suse.com/show_bug.cgi?id=1000629 I plan to merge it >> in merge_after_release and master... and it looks exactly as the kind >> of things we created self-update for. Yes, a fix for a crash looks like a good candidate for a self-update. For self-updates I'd suggest using a separate branch, e.g. "SLE-12-SP2-self-update". Another self-update related thing: The self-update overrides the original files from the inst-sys by the files from the self-update RPM. But many fixes will be located in a single file, we do not need to package the unchanged files which would override the files with the very same content. So for self-updates I'd suggest to edit the *.spec files to package only the changed files and use some suffix in the package version so it's obvious it's not a full package. (The version actually does not matter, the installer downloads and applies *all* packages regardless the version or the package dependencies.) And this is easier with a separate self-update branch. -- Best Regards Ladislav Slezák Yast Developer -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
