Just registered to give my opinion on this, as I think its a very important topic.
Currently I am suffering from this problem, as I need rust and elixir from devel repos. Also, currently am using utilities, editors for small utilities ( byobu, neovim, etc) , but put them in lower priority than opensuse tumbleweed repo. Even also, I am also using kde repo for more uptodate kde plasma versions, but i love the fact that if i want, i can go back to the stable old tumbleweed kde packages.
From one side it would be great if some packages were included in factory. But
others, I would like to keep repos for different package configurations or more edge versions.
My question is, could it be possible for devel repo owners to ask for specific tumbleweed tests to run ? For example, the kde repo would run the kde tests available in tumbleweed ? To not only be opensuse factory/tumbleweed/leap that runs tests ?
PS: do i just reply to opensuse-factory or also include the senders in CC ? Sorry if spamming your mailbox.
A quarta-feira, 13 de janeiro de 2016 13:24:16 WET Richard Brown escreveu:
On 13 January 2016 at 11:52, Bernhard M. Wiedemann firstname.lastname@example.org
Those are leaf packages that are not very critical, so probably would not be covered by openQA even if they were in Factory. Yes, they might break once in a while, but since there is only one source-code (as opposed to differing versions for 13.1, 13.2, 42.1 and Factory), it would be a lot easier and faster to fix. The point is that there are probably fewer users and thus it makes sense to have a workflow that requires less effort for the maintainer.
Or if we want to go without such a "Contrib" repo, and submit everything to Factory, we still want a Backports repo where we build all the new applications for older openSUSE versions, so that more people can use and test the new stuff.
and I guess, if we really want to, we could still add a staging+openQA ontop of either such Contrib or Backports repo.
Ciao Bernhard M.
Then lets get all those packages you are considering into Tumbleweed first
Then we can talk about the possibility of a 'contrib' repo for older distributions. I think there is a debate to had there whether a collection of untested, separately maintained packages is a good idea
- even debian is slowly abolishing 'contrib' and moving everything to
main. I think we should do the same, starting with Tumbleweed first