On 2010-11-30 23:42:37 (+0100), Klaus Kaempf
* Pascal Bleser
[Nov 30. 2010 23:24]: I think it's pretty clear how we could make rolling updates work, thanks to the awesomeness of the build service. But what should it include? The same as a shipped openSUSE release? More? Isn't it an "up-to-date and stable core system" + everything that's a stable release of anything on build.o.o ? Where do we draw the line ?
I would expect that 'subsystem maintainers' emerge, taking responsibility for specific parts of the whole distribution.
This responsibility does not only include pushing 'stable' updates to the Tumbleweed release manager but also taking care about bug reports. [...] Its up to those maintainers to draw the line, they're probably the only ones with sufficient knowledge about what might break with the update[1]. They will take the praise for up-to-date packages as well as the blame if their subsystem breaks.
Yes, that's all fine, and what I was referring to with "it's pretty
clear how we could make rolling updates work" :)
But what about the amount of packages to include into Tumbleweed then?
Same as openSUSE releases, or more?
Because as we'll be able to have Tumbleweed as a build target (or
"repository" in OBS-speak) in build.o.o, anything goes in the additional
repositories as well.
cheers
--
-o) Pascal Bleser