Feature changed by: Adrian Schröter (adrianSuSE) Feature #305907, revision 10 Title: Support Update Repo Generation Buildservice: Evaluation Priority Requester: Desirable - Projectmanager: Desirable + Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Developer: (Novell) Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-20 10:39:46) the extra informations for update channels can be stored already in _patchinfo files. We lack the generation part for it so far. -- openSUSE Feature: https://features.opensuse.org/305907

Feature changed by: Lars Vogdt (lrupp) Feature #305907, revision 13 Title: Support Update Repo Generation Buildservice: Evaluation by engineering manager Milestone: 2.3 Priority Requester: Desirable Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Project Manager: (Novell) Engineering Manager: (Novell) Developer: (Novell) Developer: (Novell) Partner organization: openSUSE.org Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. Business case (Partner benefit): openSUSE.org: Especially on openSUSE systems where the update applets only support updating if there is a patches. It's a pain because then the user will have no idea that there are updates unless they launch Software Manager in YaST (not even update manager!) or they run zypper. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-20 10:39:46) the extra informations for update channels can be stored already in _patchinfo files. We lack the generation part for it so far. + #2: Lars Vogdt (lrupp) (2011-04-20 21:37:30) + If we just lack the generation part, I like to switch to Sascha as + Developer. He should really know better than me where the current code + needs adaption and where to store the data. -- openSUSE Feature: https://features.opensuse.org/305907

Feature changed by: Adrian Schröter (adrianSuSE) Feature #305907, revision 15 Title: Support Update Repo Generation Buildservice: Done Milestone: 2.3 Priority Requester: Desirable Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. Business case (Partner benefit): openSUSE.org: Especially on openSUSE systems where the update applets only support updating if there is a patches. It's a pain because then the user will have no idea that there are updates unless they launch Software Manager in YaST (not even update manager!) or they run zypper. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-20 10:39:46) the extra informations for update channels can be stored already in _patchinfo files. We lack the generation part for it so far. #2: Lars Vogdt (lrupp) (2011-04-20 21:37:30) If we just lack the generation part, I like to switch to Sascha as Developer. He should really know better than me where the current code needs adaption and where to store the data. + #3: Adrian Schröter (adriansuse) (2012-04-17 09:12:40) + Michael implemented _patchinfo -> updateinfo.xml generation including + publishing support -- openSUSE Feature: https://features.opensuse.org/305907